This one also plagued me for a week because node-gyp could actually find my Python instance just fine, but then a later build step was not properly configured and all of the popular answers weren’t able to pick up Python. My steps to resolve on macOS Monterey (12.3.1)… $ brew install pyenv # Any modern … Read more
If this is a mac machine (OSX) here is what you can do use terminal xcode-select –print-path then remove installed version sudo rm -r -f /Library/Developer/CommandLineTools and reinstall xcode-select –install that should fix the problem Ref: gyp: No Xcode or CLT version detected macOS Catalina
Also stated in my post update, here’s the Dockerfile I used to get things working: FROM node:8.12-alpine RUN apk add g++ make py3-pip EXPOSE 8080 RUN mkdir /app WORKDIR /app COPY . /app RUN npm install CMD [“npm”, “start”] If your requirements demand your image minimize space, consider installing necessary packages with RUN apk add … Read more
I had a similar problem. I found that this switch helped me –msvs_version=2012 so for example npm install –msvs_version=2012 <package>
There’s a possible good way of doing this, depending on your setup. npm package.json supports an os key, and also optionalDependencies os can be used to specify which OS a module can be installed on. optionalDependencies are module dependencies that if they cannot be installed, npm skips them and continues installing. In this way you … Read more
I had the same problem with another module. I solved it by: Install visual studio community 2013 Run npm config set msvs_version 2013 –global Run npm install bcrypt
node-gyp is a tool which compiles Node.js Addons. Node.js Addons are native Node.js Modules, written in C or C++, which therefore need to be compiled on your machine. After they are compiled with tools like node-gyp, their functionality can be accessed via require(), just as any other Node.js Module. If you do what you suggested … Read more
Try that – will set it globally: npm config set msvs_version 2012 –global
so this happened to me on windows recently. I fix it by following the following steps using a PowerShell with admin privileges: delete node_modulesfolder running npm install –global windows-build-tools with administrative privilege. (in my case need restart – and restart without ask!!!) reinstalling node modules or node-sass with npm install
Even though you have them installed (my case), but by upgrading to Catalina (10.15.*) you can get this error (my case 🙂 ). Therefore, simply installing wouldn’t help as you will get an error that they are already installed. Therefore you need to hopefully just (I) reset the tool or in worse case (II) uninstall … Read more