Forum Discussion
Wildtypitch
Jan 29, 2021Copper Contributor
Sharepoint development framework environment setup. Yeoman crashing, install warnings
Following the guide https://docs.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment made sure of all the prerequisites but as I follow the steps I get multiple warnings to d...
waldek
Microsoft
Feb 01, 2021Are you running PowerShell as admin? You’re in the system32 directory. Have you tried creating project in a different folder?
- WildtypitchFeb 01, 2021Copper Contributor
Sadly it doesn't seem to make a difference. I've tried in a project folder
PS D:\sharepoint\sp-site-designs-studio-master> node - PS D:\sharepoint\sp-site-designs-studio-master> node -v v10.23.2 PS D:\sharepoint\sp-site-designs-studio-master> npm -v 6.14.10 PS D:\sharepoint\sp-site-designs-studio-master> npm install -g yo gulp npm : npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. At line:1 char:1 + npm install -g yo gulp + ~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (npm WARN deprec...s dependencies.:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError 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 fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated cross-spawn-async@2.2.5: cross-spawn no longer requires a build toolchain, use it instead C:\Users\natha\AppData\Roaming\npm\gulp -> C:\Users\natha\AppData\Roaming\npm\node_modules\gulp\bin\gulp.js C:\Users\natha\AppData\Roaming\npm\yo -> C:\Users\natha\AppData\Roaming\npm\node_modules\yo\lib\cli.js C:\Users\natha\AppData\Roaming\npm\yo-complete -> C:\Users\natha\AppData\Roaming\npm\node_modules\yo\lib\completion\index.js > yo@3.1.1 postinstall C:\Users\natha\AppData\Roaming\npm\node_modules\yo > yodoctor Yeoman Doctor Running sanity checks on your system √ No .bowerrc file in home directory √ Global configuration file is valid √ NODE_PATH matches the npm root √ No .yo-rc.json file in home directory √ Node.js version √ npm version √ yo version Everything looks all right! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules\gulp\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"}) + yo@3.1.1 + gulp@4.0.2 updated 3 packages in 18.739s
all the same warnings installing gulp and yo
When trying to create the project
PS D:\sharepoint\sp-site-designs-studio-master> yo @microsoft/sharepoint node.exe : At C:\Users\natha\AppData\Roaming\npm\yo.ps1:15 char:3 + & "node$exe" "$basedir/node_modules/yo/lib/cli.js" $args + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError _-----_ | | .--------------------------. |--(o)--| [0m|[0m [0mWelcome to the[0m [0m|[0m `---------´ [0m|[0m [0m[34mS[34mh[34ma[34mr[34me[34mP[34mo[34mi[34mn[34mt[34m [34mC[34ml[34mi[34me[34mn[34mt[34m-[34ms[34mi[34md[34me[0m [0m|[0m ( _´U`_ ) [0m|[0m [0m[34mS[34mo[34ml[34mu[34mt[34mi[34mo[34mn[34m [34mG[34me[34mn[34me[34mr[34ma[34mt[34mo[34mr[0m [0m|[0m /___A___\ [0m'--------------------------' | ~ | __'.___.'__ ´ ` |° ´ Y ` Let's create a new SharePoint solution.
- Victoria GelinasFeb 13, 2022Copper ContributorDid you ever resolve your issue as I am having the same issue? I have uninstalled and reinstalled node several times. Whenever I try yo to generate a new project it just hangs exactly how you have it above. I have tried to reinstall the sharepoint generator and also yo but I get errors. I have removed all traces of node, npm, all of the cache several times and still the same errors.
- waldekFeb 01, 2021
Microsoft
How have you installed node? Perhaps something went wrong there? As a last resort, you could try to remove yo and gulp (npm uninstall -g yo gulp) and then uninstall Node and reinstall everything again?- WildtypitchFeb 01, 2021Copper ContributorThat's what I'm in the process of doing right now. It's possible there are hidden conflicting versions of node. So I'm trying to remove all traces of it and starting again.
- WildtypitchFeb 01, 2021Copper ContributorThanks for the reply. Hi using powershell use as admin yes. Right I shouldn't be doing things in there. I'll give it a try this morning.