Forum Discussion
Error: Cannot find module '@microsoft/sp-build-web'
- Feb 07, 2020
From your picture, I can see that you are using node version 13, which is not currently supported. Download version 10 and that should resolve the issue.
Hi Joel Rodrigues,
Thanks for looking into it again. My OS is Windows 10, and other version details are in below image
rashics not really sure. Do you know if you have python installed?
Try installing windows build tools:
npm install --global --production windows-build-tools
- rashicsJul 31, 2021Copper ContributorHi FreddieS1685,
You may fine the below location for that binding node file.
https://github.com/sass/node-sass/releases/download/v4.14.1/win32-x64-83_binding.node - FreddieS1685Jul 30, 2021Copper Contributor
rashics hey man, can you share where did you get that "blinding.node" file please?
- rashicsJul 23, 2020Copper Contributor
Hi Joel Rodrigues,
Thanks for sharing that proxy issue details, but was not able to solve with it, may be unable to setup proxy settings properly. But now gulp serve issue is solved after installing one file("binding.node") manually from the github site and placed in the node module folder under <path>/helloworld-webpart\node_modules\node-sass\vendor\win32-x64-64
Thank you again for your help.
- Jul 13, 2020
Hi rashics that seems like a proxy issue with npm.
Are you behind a corporate proxy? If so, try to explicitly configure the proxy within npm. I have never done this myself, but hopefully, the below can help or be used as a starting point
https://stackoverflow.com/questions/33162560/error-tunneling-socket-while-executing-npm-install
Once you configure npm with the proxy information, try to install windows build tools again.
- rashicsJul 13, 2020Copper Contributor
Hi Joel Rodrigues,
Thank you for looking it again. I ran that command and below is the failed output.
Please suggests what can be done next to solve all this? Is there any installation issue. First time, it worked on my machine, but after some days, when tried to create again with new sample webpart, I am facing these issues now and unable to run any new sample webpart.