windows-build-tools | :package: Install C++ Build Tools for Windows using npm | Runtime Evironment library

You need to check if the node version installed in your machine is compatible with the node-sass version installed in the project.

In your terminal do node -v to check your node version and look at the node-sass version of the cloned project in the package.json file. Look at the following answer for more information on what version of node-sass is compatible with what version of node.

Check this answer https://stackoverflow.com/a/67778126/9241178

For me, running npm i -g windows-build-tools from a command line with administrator privileges would hang during installation, but I was able to navigate to C:\Users\[username]\.windows-build-tools and run the .exe file from there. This worked its magic, and I was able to run npm install as normal.

After trying for several weeks I eventually gave up. The best way to avoid this error is simply to install Phoenix's newest version: https://hexdocs.pm/phoenix/installation.html

Which does not use SASS and therefore wont need NodeJS to compile.

I ended up creating a fresh project and porting my old code there. Not the best experience.

Node version could be a problem. That windows-build-tools is required for the installation indicates there's binary dependency that is potentially incompatible with current Node version. Binary NPM dependencies usually provide a subset of precompiled binaries for a specific package version, where a combination of platform and Node.js version that can be considered safe or supported. For any other combination, binary package needs to be compiled for current platform with build tools. This doesn't always mean that the package is incompatible but this is common.

For example, node-sass (doesn't seem to be used here) has different versions that correspond to specific Node.js versions and provides precompiled binaries for a supported subset; for unsupported Node.js version it falls back to compilation during installation process and most likely fails.

It's unknown which dependency causes this problem in this case, this needs to be reviewed in npm/yarn logs.

In order to avoid this situation, Node version could be matched with old one. Project dependencies need to be freshly installed because node_modules in use has been already tied to currently used Node version.

I found the problem after hours of searching, it was my node version, i was at 16.x.x, I installed node version manager and moved to version 14 and it worked.

How much more clear can npm be?!

Error: not found: c:\python27\python.exe

some packages require python2.7; others look for python and will accept Python 3. It's a pain; especially for those of us that don't use Python otherwise. But your problem is basic - install Python and try again

My Problem is msvs version not set as it says in the error msvs_version does not match this version I run

Step 1 - Check if you have a virtual environment, if not (python -m venv “location of project”) Step 2 - Select interpreter since virtual environment is created(in Visual Studio code its ctrl+shift+p ) then click "select interpreter", then select "enter interpreter path", then select "browse your file system to find a python interpreter", then goto the installed virtual environment the select the python.exe file Step 3 - open terminal in VS code, then in file path goto script folder(cd Scripts) then enter ".\activate" Step 4 - pip install npm

Hopefully this works for you

From the NPM page at https://www.npmjs.com/package/windows-build-tools