(Remember this is under $HOME so the command doesn’t require any special permissions like sudo) Using vim $ code ~/.node-gyp//include/node/common.gypi

Yes you can also use it to edit shady config files, just Save the file as usual when you’re done. The most underrated editor ever: $ nano ~/.node-gyp//include/node/common.gypi Using VS Code

Open the file, find the MACOSX_DEPLOYMENT_TARGET key value and replace it with your current Mac OS version ( 10.15.3 for Catalina for example).Įxamples with different editors: Using nano (Remember ~ means your user’s $HOME directory) You’ll usually find it in a path like: ~/.node-gyp//include/node/common.gypiĮxample for NodeJs 6.5.0: ~/.node-gyp/6.5.0/include/node/common.gypi You’ll need to find and edit the common.gypi file for the NodeJs version you’re using. If the most complex node-gyp-related dependency you have in your project is something common like node-sass then this is usually the fix you need. If your project has any complex dependencies that rely heavily on native libraries this solution might not be for you. Just for context, this issue usually happens after upgrading your OS of if you use nvm and are using a newly installed NodeJs version. It often times comes accompanied with an error message like: fatal error: 'utility' file not found #include Īnother usual fix is to reinstall XCode’s command-line tools with: $ xcode-select -install This issue is usually caused because a node-gyp config file called common.gypi is not set up for your current Mac OS version.

Nvm mac os