Can't install @microsoft/sp-build-web

%3CLINGO-SUB%20id%3D%22lingo-sub-1592025%22%20slang%3D%22en-US%22%3ECan't%20install%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F41501%22%20target%3D%22_blank%22%3E%40microsoft%3C%2FA%3E%2Fsp-build-web%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1592025%22%20slang%3D%22en-US%22%3E%3CP%3ENB%3A%20I've%20seen%20a%20similar%20post%20to%20mine%20from%20the%20beginning%20of%20the%20year%2C%20nothing%20in%20there%20helped.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAbout%206-8%20months%20ago%20I%20was%20able%20to%20get%20the%20sp%20Framework%20working%20on%20my%20pc%20at%20work%20(behind%20a%20proxy%2C%20*sigh*%20many%20problems%20there%2C%20but%20got%20there%20in%20the%20end)%20and%20I%20was%20able%20to%20get%20the%20Hello%20World%20Web%20Part%20onto%20the%20workbench%20on%20my%20(personal)%20developer%20tenant%2C%20plus%20experiment%20with%20a%20few%20more%20complex%20things%2C%20all%20worked%20fine.%26nbsp%3B%20My%20org%20is%20still%20not%20quite%20ready%20for%20SP%20online%20but%20getting%20closer%2C%20so%20..%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20now%20revisiting%20the%20SP%20Framework%20process%20after%20a%20long%20break%2C%20same%20pc%2C%26nbsp%3BI%20think%20last%20time%20the%20recommended%20Node%20version%20was%208.something%2C%20now%20you%20recommend%2010%20LTS%2C%20so%20I'm%20running%2010.22.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGot%20the%20latest%20yo%20package%20etc%2C%20and%20am%20trying%20this%20time%20to%20again%20create%20a%20web%20part%20with%20'no%20javascript%20framework'.%26nbsp%3B%20%26nbsp%3BInstall%20always%20fails%20at%20the%20point%20of%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F41501%22%20target%3D%22_blank%22%3E%40microsoft%3C%2FA%3E%2Fsp-build-web%2C%20error%20message%20below%20(from%20trying%20to%20install%20this%20package%20on%20its%20own)%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-bash%22%3E%3CCODE%3EPS%20C%3A%5Cmyproject%26gt%3B%20npm%20i%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F41501%22%20target%3D%22_blank%22%3E%40microsoft%3C%2FA%3E%2Fsp-build-web%401.8.2%0Anpm%20WARN%20deprecated%20fsevents%401.2.13%3A%20fsevents%201%20will%20break%20on%20node%20v14%2B%20and%20could%20be%20using%20insecure%20binaries.%20Upgrade%20to%20fsevents%202.ing%20insecure%20binaries.%20Upgrade%20to%20fsevents%202.%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20if%20you%20prefer%20the%20old%20syntax.%20Visit%20%26lt%3B%26gt%3B%20for%20migration%20path%0Anpm%20WARN%20deprecated%20kleur%402.0.2%3A%20Please%20upgrade%20to%20kleur%403%20or%20migrate%20to%20'ansi-colors'%0Aif%20you%20prefer%20the%20old%20syntax.%20Visit%20%26lt%3B%26gt%3B%20for%20migration%20path(s).%0Anpm%20WARN%20optional%20SKIPPING%20OPTIONAL%20DEPENDENCY%3A%20fsevents%40%5E1.2.3%20(node_modules%5C%40microsoft%5Csp-build-web%5Cnode_modules%5Csane%5Cnode_modules%5Cfsevents)%3A%0Anpm%20WARN%20notsup%20SKIPPING%20OPTIONAL%20DEPENDENCY%3A%20Unsupported%20platform%20for%20fsevents%401.2.13%3A%20wanted%20%7B%22os%22%3A%22darwin%22%2C%22arch%22%3A%22any%22%7D%20(current%3A%20%7B%22os%22%3A%22win32%22%2C%22arch%22%3A%22x64%22%7D)%0Anpm%20WARN%20optional%20SKIPPING%20OPTIONAL%20DEPENDENCY%3A%20fsevents%40%5E1.2.3%20(node_modules%5C%40microsoft%5Cgulp-core-build-sass%5Cnode_modules%5Csane%5Cnode_modules%5Cfsevents)%3A%0Anpm%20WARN%20notsup%20SKIPPING%20OPTIONAL%20DEPENDENCY%3A%20Unsupported%20platform%20for%20fsevents%401.2.13%3A%20wanted%20%7B%22os%22%3A%22darwin%22%2C%22arch%22%3A%22any%22%7D%20(current%3A%20%7B%22os%22%3A%22win32%22%2C%22arch%22%3A%22x64%22%7D)%0A%0Anpm%20ERR!%20code%20ENOVERSIONS%0Anpm%20ERR!%20No%20valid%20versions%20available%20for%20undefined%0A%0Anpm%20ERR!%20A%20complete%20log%20of%20this%20run%20can%20be%20found%20in%3A%0Anpm%20ERR!%20%20%20%20%20c%3A%5CProgramData%5Cnpm-cache%5C_logs%5C2020-08-17T01_55_38_450Z-debug.log%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20valid%20versions%20of%20...%20what%3F%20From%20where%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIdeas%2Fthoughts%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1747799%22%20slang%3D%22en-US%22%3ERe%3A%20Can't%20install%20%3Ca%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F41501%22%3E%40microsoft%3C%2Fa%3E%2Fsp-build-web%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1747799%22%20slang%3D%22en-US%22%3E%3CP%3EResolved%20this%20eventually%20by%20adding%20%3CSTRONG%3E--no-cache%3C%2FSTRONG%3E%20to%20the%20install%20line.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBecause%20of%26nbsp%3Bfrustrating%20time-outs%20imposed%20by%20my%20org's%20proxy%26nbsp%3Bwhen%20I%20first%20tested%20the%20framework%20last%20year%2C%26nbsp%3BI%20had%20to%20set%20node%20to%20prefer%20the%20locally%20cached%20version%20of%20a%20package%20if%20it%20existed.%26nbsp%3B%20I%20would%20install%20til%20the%20time%20out%2C%20pick%20up%20where%20I%20left%20off%2C%20etc%20etc.%26nbsp%3B%26nbsp%3BEventually%20everything%20came%20through%20and%20worked%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20that%20my%20org%20proxy%20situation%20has%20improved%2C%20and%20additionally%20I've%20added%20Fiddler%20into%20the%20mix%20to%20keep%20the%20connections%20open%20and%20smooth%2C%20I%20thought%20I%20had%20disabled%20the%20'prefer%20cache'%20setting%20but%20it%20seems%20I%20hadn't%20done%20enough.%26nbsp%3B%26nbsp%3BForcing%20the%20install%20to%20bypass%20the%20cache%20enabled%20me%20to%20fully%20and%20successfully%20install%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F41501%22%20target%3D%22_blank%22%3E%40microsoft%3C%2FA%3E%2Fsp-build-web.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

NB: I've seen a similar post to mine from the beginning of the year, nothing in there helped.

 

About 6-8 months ago I was able to get the sp Framework working on my pc at work (behind a proxy, *sigh* many problems there, but got there in the end) and I was able to get the Hello World Web Part onto the workbench on my (personal) developer tenant, plus experiment with a few more complex things, all worked fine.  My org is still not quite ready for SP online but getting closer, so .. 

 

I'm now revisiting the SP Framework process after a long break, same pc, I think last time the recommended Node version was 8.something, now you recommend 10 LTS, so I'm running 10.22.  

 

Got the latest yo package etc, and am trying this time to again create a web part with 'no javascript framework'.   Install always fails at the point of @microsoft/sp-build-web, error message below (from trying to install this package on its own):

 

PS C:\myproject> npm i @microsoft/sp-build-web@1.8.2
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.ing insecure binaries. Upgrade to fsevents 2.                                          if you prefer the old syntax. Visit <https://github.com/lukeed/kleur/releases/tag/v3.0.0\> for migration path
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.t\sp-build-web\node_modules\sane\node_modules\fsevents):0\> for migration path(s).
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.3 (node_modules\@microsoft\sp-build-web\node_modules\sane\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 optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.3 (node_modules\@microsoft\gulp-core-build-sass\node_modules\sane\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 ERR! code ENOVERSIONS
npm ERR! No valid versions available for undefined

npm ERR! A complete log of this run can be found in:
npm ERR!     c:\ProgramData\npm-cache\_logs\2020-08-17T01_55_38_450Z-debug.log

 

 

No valid versions of ... what? From where?

 

Ideas/thoughts?

 

1 Reply

Resolved this eventually by adding --no-cache to the install line.

 

Because of frustrating time-outs imposed by my org's proxy when I first tested the framework last year, I had to set node to prefer the locally cached version of a package if it existed.  I would install til the time out, pick up where I left off, etc etc.  Eventually everything came through and worked fine.

 

Now that my org proxy situation has improved, and additionally I've added Fiddler into the mix to keep the connections open and smooth, I thought I had disabled the 'prefer cache' setting but it seems I hadn't done enough.  Forcing the install to bypass the cache enabled me to fully and successfully install @microsoft/sp-build-web.