Getting Started With Web Parts

[scottrayrader]

NPM Errors

• [x] Question

I am a newbie here, so I hope I'm putting this in the right spot and that you guys take it easy on me! I'm brand-new to the site and using a web part from the site. I got started by doing the Microsoft tutorial creating the Hello Webpart. It worked fine. I then downloaded some files for another webpart that I wanted to do. I got an error message. I went through and tried to delete things that I had installed. I uninstalled some things through windows power shell and programs through the control panel that are required for setting up your developmental environment.

I went back to square one and started with the Hello Webpart tutorial (reinstalled everything) and I am now getting NPM errors. I would just like to get back to square one with being able to install it without any errors like I did the very first time I went through the process.

Windows 10 SharePoint Online .NET Framework v 4.8x Chrome 83

Please see attached text document.

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[scottrayrader]

I could not tell if the attachment went through. Here is the text from it:

After I give it the commands to create the hello world web part these errors now show up.

npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5 npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x. npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart() npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated core-js@1.2.7: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3. npm WARN deprecated es6-collections@0.5.6: not actively maintained anymore npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2. npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated kleur@2.0.2: Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s). npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated mkdirp-promise@5.0.1: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that. npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

Then, right before it tells me it is finished and I can run the gulp serve command these error messages are showing up.

Binary found at C:\helloworld-webpart\node_modules\node-sass\vendor\win32-x64-64\binding.node Testing binary Binary is fine npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN notsup Unsupported engine for watchpack-chokidar2@2.0.0: wanted: {"node":"<8.10.0"} (current: {"node":"10.20.1","npm":"6.14.4"}) npm WARN notsup Not compatible with your version of node/npm: watchpack-chokidar2@2.0.0 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules\watchpack\node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN ajv-keywords@3.4.1 requires a peer of ajv@^6.9.1 but none is installed. You must install peer dependencies yourself. npm WARN uglifyjs-webpack-plugin@0.4.6 requires a peer of webpack@^1.9 || ^2 || ^2.1.0-beta || ^2.2.0-rc || ^3.0.0 but none is installed. You must install peer dependencies yourself.

[Jerry0527]

What's the details you want to get from another web part ? If you want to use some third party api like pnp.js , just use npm install. Currently, can you create a new web part using yo @microsoft/sharepoint in your environment ?

[scottrayrader]

This is what I did. I just went through the Microsoft tutorial and created the hello web part. The yeoman generator worked fine.

This is the web part that I am now trying to create: https://tahoeninjas.blog/2018/06/05/creating-a-calendar-feed-web-part-part-ii/. When I get to step three to run the yeoman generator here air message that I get:

PS C:> cd react-calendar-feed-1 PS C:\react-calendar-feed-1> yo @Microsoft/sharepoint Error @Microsoft/sharepoint

You don't seem to have a generator with the name “@Microsoft/sharepoint” installed. But help is on the way:

You can see available generators via npm search yeoman-generator or via http://yeoman.io/generators/. Install them with npm install @Microsoft/generator-sharepoint.

To see all your installed generators run yo without any arguments. Adding the --help option will also show subgenerators.

If yo cannot find the generator, run yo doctor to troubleshoot your system. PS C:\react-calendar-feed-1>

[Jerry0527]

The command is case sensitive, please modify as below, "m" for microsoft should be lower case:

yo @microsoft/sharepoint

[scottrayrader]

Thank you for your help.

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues