Node gyp rebuild error on windows 10

more info. Running via Teriminal and editing script to show info.

   ajink@LAPTOP-018O850F ~ ❯❯❯ node-gyp configure --msvs_version=2022
gyp info it worked if it ends with ok
gyp info using node-gyp@9.0.0
gyp info using node@16.13.2 | win32 | x64
gyp info find Python using Python version 3.10.0 found at "C:Python310python.exe"
Ajinkya was here
[
  {
    path: 'C:\Program Files\Microsoft Visual Studio\2022\Community',
    version: '17.1.32210.238',
    packages: [
      'Microsoft.VisualStudio.Component.VC.14.30.17.0.x86.x64',
      'Microsoft.VC.14.30.17.0.Tools.HostX64.TargetX86',
      'Microsoft.VC.14.30.17.0.Premium.Tools.HostX64.TargetX86',
      'Microsoft.VC.14.30.17.0.Premium.Tools.HostX64.TargetX86.base',
      'Microsoft.VC.14.30.17.0.Premium.Tools.HostX64.TargetX86.Resources.base',
      'Microsoft.VC.14.30.17.0.Tools.HostX86.TargetX64',
      'Microsoft.VC.14.30.17.0.Premium.Tools.HostX86.TargetX86',
      'Microsoft.VC.14.30.17.0.Premium.Tools.HostX86.TargetX86.base',
      'Microsoft.VC.14.30.17.0.Premium.Tools.HostX86.TargetX86.Resources.base',
      'Microsoft.VC.14.30.17.0.Premium.Tools.HostX86.TargetX64',
      'Microsoft.VC.14.30.17.0.Premium.Tools.HostX86.TargetX64.base',
      'Microsoft.VC.14.30.17.0.Premium.Tools.Hostx86.Targetx64.Resources.base',
      'Microsoft.VC.14.30.17.0.PGO.X86',
      'Microsoft.VC.14.30.17.0.PGO.X86.base',
      'Microsoft.VC.14.30.17.0.PGO.X64',
      'Microsoft.VC.14.30.17.0.PGO.X64.base',
      'Microsoft.VC.14.30.17.0.CRT.x86.Store',
      'Microsoft.VC.14.30.17.0.CRT.x86.Store.base',
      'Microsoft.VC.14.30.17.0.CRT.x86.OneCore.Desktop',
      'Microsoft.VC.14.30.17.0.CRT.x86.OneCore.Desktop.base',
      'Microsoft.VC.14.30.17.0.CRT.x86.Desktop',
      'Microsoft.VC.14.30.17.0.CRT.x86.Desktop.base',
      'Microsoft.VC.14.30.17.0.CRT.x64.Store',
      'Microsoft.VC.14.30.17.0.CRT.x64.Store.base',
      'Microsoft.VC.14.30.17.0.CRT.x64.OneCore.Desktop',
      'Microsoft.VC.14.30.17.0.CRT.x64.OneCore.Desktop.base',
      'Microsoft.VC.14.30.17.0.CRT.x64.Desktop',
      'Microsoft.VC.14.30.17.0.CRT.x64.Desktop.base',
      'Microsoft.VC.14.30.17.0.CRT.Redist.x86.OneCore.Desktop',
      'Microsoft.VC.14.30.17.0.CRT.Redist.x86.OneCore.Desktop.base',
      'Microsoft.VC.14.30.17.0.CRT.Redist.X86',
      'Microsoft.VC.14.30.17.0.CRT.Redist.X86.base',
      'Microsoft.VC.14.30.17.0.CRT.Redist.x64.OneCore.Desktop',
      'Microsoft.VC.14.30.17.0.CRT.Redist.x64.OneCore.Desktop.base',
      'Microsoft.VC.14.30.17.0.CRT.Redist.X64',
      'Microsoft.VC.14.30.17.0.CRT.Redist.X64.base',
      'Microsoft.VC.14.30.17.0.ASAN.X86',
      'Microsoft.VC.14.30.17.0.ASAN.X86.base',
      'Microsoft.VC.14.30.17.0.Tools.HostX64.TargetX86.base',
      'Microsoft.VC.14.30.17.0.Tools.HostX64.TargetX86.Resources.base',
      'Microsoft.VC.14.30.17.0.ASAN.X64.base',
      'Microsoft.VC.14.30.17.0.Tools.HostX86.TargetX64.base',
      'Microsoft.VC.14.30.17.0.Tools.Hostx86.Targetx64.Resources.base',
      'Microsoft.VC.14.30.17.0.ASAN.Headers.base',
      'Microsoft.VC.14.30.17.0.Tools.HostX64.TargetX64',
      'Microsoft.VisualStudio.Component.VC.Tools.ARM',
      'Microsoft.VisualCpp.Tools.HostX86.TargetARM.Resources',
      'Microsoft.VisualCpp.Tools.Hostx86.Targetarm',
      'Microsoft.VC.14.31.17.1.Tools.Hostx86.Targetarm.base',
      'Microsoft.VC.14.31.17.1.Tools.HostX86.TargetARM.Resources.base',
      'Microsoft.VisualCpp.CRT.Redist.arm.OneCore.Desktop',
      'Microsoft.VC.14.31.17.1.CRT.Redist.arm.OneCore.Desktop.base',
      'Microsoft.VisualCpp.CRT.arm.Store',
      'Microsoft.VC.14.31.17.1.CRT.arm.Store.base',
      'Microsoft.VisualCpp.CRT.arm.Desktop',
      'Microsoft.VC.14.31.17.1.CRT.arm.Desktop.base',
      'Microsoft.VisualStudio.PackageGroup.VC.Tools.x64.ARM',
      'Microsoft.VisualCpp.Premium.Tools.Hostx86.Targetarm',
      'Microsoft.VC.14.31.17.1.Premium.Tools.Hostx86.Targetarm.base',
      'Microsoft.VC.14.31.17.1.Premium.Tools.HostX86.TargetARM.Resources.base',
      'Microsoft.VisualCpp.Premium.Tools.HostX64.TargetARM',
      'Microsoft.VC.14.31.17.1.Premium.Tools.HostX64.TargetARM.base',
      'Microsoft.VC.14.31.17.1.Premium.Tools.HostX64.TargetARM.Resources.base',
      'Microsoft.VisualCpp.Premium.Tools.ARM.Base',
      'Microsoft.VC.14.31.17.1.Premium.Tools.ARM.Base.base',
      'Microsoft.VC.14.31.17.1.Premium.Tools.ARM.Base.Resources.base',
      'Microsoft.VisualCpp.PGO.ARM',
      'Microsoft.VC.14.31.17.1.PGO.ARM.base',
      'Microsoft.VisualCpp.Tools.HostX64.TargetARM',
      'Microsoft.VC.14.31.17.1.Tools.HostX64.TargetARM.base',
      'Microsoft.VC.14.31.17.1.Tools.HostX64.TargetARM.Resources.base',
      'Microsoft.VC.14.31.17.1.Props.ARM',
      'Microsoft.VisualCpp.CRT.arm.OneCore.Desktop',
      'Microsoft.VC.14.31.17.1.CRT.arm.OneCore.Desktop.base',
      'Microsoft.VC.14.31.17.1.ATL.Headers.base',
      'Microsoft.VC.14.31.17.1.Servicing.ATL',
      'Microsoft.VisualStudio.Component.VC.CMake.Project',
      'Microsoft.VisualStudio.ComponentGroup.WebToolsExtensions.CMake',
      'Microsoft.VisualStudio.VC.Ide.LanguageService',
      'Microsoft.VisualStudio.VC.CMake',
      'Microsoft.VisualStudio.Cache.Service',
      'Microsoft.VisualStudio.VC.CMake.Project',
      'Microsoft.VisualStudio.VC.Ide.ResourceEditor',
      'Microsoft.VisualStudio.VC.Ide.ResourceEditor.Resources',
      'Microsoft.VisualStudio.VC.CMake.Client',
      'Microsoft.VisualStudio.VC.Ide.VCPkgDatabase',
      'Microsoft.VisualStudio.VC.ExternalBuildFramework',
      'Microsoft.VisualStudio.VC.Ide.Progression.Enterprise',
      'Microsoft.VisualStudio.VisualC.Utilities',
      'Microsoft.VC.14.30.17.0.Tools.HostX64.TargetX64.base',
      'Microsoft.VC.14.30.17.0.Props.x64',
      'Microsoft.VisualStudio.VC.Ide.Common',
      'Microsoft.VisualStudio.VC.MSVCDis',
      'Microsoft.VC.14.30.17.0.Tools.HostX64.TargetX64.Resources.base',
      'Microsoft.VC.14.30.17.0.Premium.Tools.HostX64.TargetX64',
      'Microsoft.VC.14.30.17.0.Premium.Tools.HostX64.TargetX64.base',
      'Microsoft.VisualStudio.VC.Ide.Base',
      'Microsoft.VC.14.30.17.0.Premium.Tools.HostX64.TargetX64.Resources.base',
      'Microsoft.VisualCpp.Tools.Common.Utils.Resources',
      'Microsoft.VisualStudio.VirtualTree',
      ... 535 more items
    ]
  }
]
gyp ERR! find VS
gyp ERR! find VS msvs_version was set from command line or npm config
gyp ERR! find VS - looking for Visual Studio version 2022
gyp ERR! find VS running in VS Command Prompt, installation path is:
gyp ERR! find VS "C:Program Files (x86)Microsoft Visual Studio2022"
gyp ERR! find VS - will only use this version
gyp ERR! find VS checking VS2022 (17.1.32210.238) found at:
gyp ERR! find VS "C:Program FilesMicrosoft Visual Studio2022Community"
gyp ERR! find VS - found "Visual Studio C++ core features"
gyp ERR! find VS - found VC++ toolset: v143
gyp ERR! find VS - found Windows SDK: 10.0.19041.0
gyp ERR! find VS - does not match this Visual Studio Command Prompt
gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS msvs_version does not match this VS Command Prompt or the
gyp ERR! find VS installation cannot be used.
gyp ERR! find VS
gyp ERR! find VS **************************************************************
gyp ERR! find VS You need to install the latest version of Visual Studio
gyp ERR! find VS including the "Desktop development with C++" workload.
gyp ERR! find VS For more information consult the documentation at:
gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows
gyp ERR! find VS **************************************************************
gyp ERR! find VS
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Visual Studio installation to use
gyp ERR! stack     at VisualStudioFinder.fail (C:ProgramDatanvmv16.13.2node_modulesnode-gyplibfind-visualstudio.js:122:47)
gyp ERR! stack     at C:ProgramDatanvmv16.13.2node_modulesnode-gyplibfind-visualstudio.js:75:16
gyp ERR! stack     at VisualStudioFinder.findVisualStudio2013 (C:ProgramDatanvmv16.13.2node_modulesnode-gyplibfind-visualstudio.js:367:14)
gyp ERR! stack     at C:ProgramDatanvmv16.13.2node_modulesnode-gyplibfind-visualstudio.js:71:14
gyp ERR! stack     at C:ProgramDatanvmv16.13.2node_modulesnode-gyplibfind-visualstudio.js:388:16
gyp ERR! stack     at C:ProgramDatanvmv16.13.2node_modulesnode-gyplibutil.js:54:7
gyp ERR! stack     at C:ProgramDatanvmv16.13.2node_modulesnode-gyplibutil.js:33:16
gyp ERR! stack     at ChildProcess.exithandler (node:child_process:404:5)
gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
gyp ERR! stack     at maybeClose (node:internal/child_process:1064:16)
gyp ERR! System Windows_NT 10.0.19044
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\node-gyp\bin\node-gyp.js" "configure" "--msvs_version=2022"
gyp ERR! cwd C:Usersajink
gyp ERR! node -v v16.13.2
gyp ERR! node-gyp -v v9.0.0
gyp ERR! not ok

Getting Node-gyp working on windows 10

( trying to take the least complicated path )

If the above didn’t work» go to https://github.com/Microsoft/nodejs-guidelines/blob/master/windows-environment.md#compiling-native-addon-modules

If I just run node-gyp, I get

Cannot find module:

‘C:Program Filesnodejsnode_modulesnpmnode_modulesnode_modulesnode-gypbinnode-gyp.js’ ( etc ). Even though that file exists.

ERR! stack Error: msbuild failed with exit code: 1 gyp ERR! stack at ChildProcess.onExit (C:Program Filesnodejsnode_modulesnpmnode_modulesnode-gyplibbuild.js:258:23)

Any ideas where to go from here?

5 Answers 5

your node-gyp module is initialised from the NPM but there is a fair chance that its correct path is not added to the environment variables in your system, Just add it to the system variables. Check the path variable if it has «C://Users/abc/AppData/Roaming/npm» if not, Please add it.

Also check if python is added to your environment variable.

It seems fairly easy to miss some step when you already have a Visual Studio environment and one or more versions of Python installed.

I will try to synthesise here the steps that worked for me.

CONTEXT

Below the details as per configuration:

Guideline

You might have already walked through some of the steps outlined here. If you incurred in some issues, you may be able to identify at which stage something went wrong by reviewing the steps in detail:

References

(1) Node.js

This guideline assumes that git is already installed in your machine (you will find the installer for Windows here anyways).

(2) npm

Run as Administrator a PowerShell terminal:

You will be prompted to choose a version. The greatest available version among the options should be fine.

If you miss this package you might want to follow the instructions to install it by following the steps outlined in the GitHub repository, which basically are to type the following in a PowerShell console running as Administrator:

(3) Visual Studio

If you have Visual Studio already installed, you might skip this step, unless you wanted to also upgrade to the newest version.

In some posts, you might have read that you can achieve this step by simply using the following command line, after installing node-gyp :

However, you could opt to achieve this by other means:

This is really up to you. At a later stage, in this guideline, we will walk through the steps to configure the node-gyp to use a specific Visual Studio version.

(4) Python

In the installation guideline for node-gyp (GitHub official repo) specifies which versions of Python are currently compatible with the latest node-gyp version on Unix and macOS. However it does not explain for Windows platforms (as at 1st of March 2020).

Although lack of documentation on this point, by having a look at other users’ issues with this, it is fair to assume that on Windows platforms, node-gyp is only supported for Python v2.7.X (reference).

(5) node-gyp

Now it is the moment to correctly set up your node-gyp configuration.

If you haven not installed it as yet:

(5.1) Set the Python version

According the documentation:

If the NODE_GYP_FORCE_PYTHON environment variable is set to the path of a Python executable, it will be used instead of any of the other configured or builtin Python search paths. If it’s not a compatible version, no further searching will be done.

Alternatively you can use the command line below:

(5.2) Set the Visual Studio Build Tools version

This step should be fairly easy:

For example, if you want it to use the MSBuild of 2019, use the command below:

That must have done it.

(6) Testing node-gyp by creating a simple add-on in C++

References

Hands on work

In a test folder, create testhello_module subfolder with the following empty files:

Now fill the files in with the contents specified below. Please, leave the index.js for the end, since we will be compiling before using it.

The hello.cc file content:

The binding.gyp file content:

You can leave the index.js file for the end.

Now, let’s build the project:

The testhello_modulebuild folder should have been created with the basic project files to compile a C++ solution (this is what node-gyp basically aims to: that you can use any C++ compiler without having to use the GUI ; in this case Visual Studio ).

Now, let’s build the addon:

At the end of both commands you should read gyp info ok to know that everything was okay (you might not see it on a PowerShell terminal because of the blue background; if so, you can edit the Properties of the window and change Screen Background to black).

This command should have created the testhello_modulebuildRelease folder with the hello.node file.

Notes:

(7) Wrap and use the add-on in C++

This is an extra step. As you might have got here, why leaving it like this?

Now let’s write the wrapper hello_moduleindex.js file:

And in the test folder, create the testhello_world.js file that uses our addon:

And in the terminal:

You should see Hello World! prompted on the screen.

Hope this helps anyone having issues to identify where exactly the configuration of node-gyp failed to meet requirements.

Источник

Building Autodesk Forge RCDB on Windows 10 fails with node-gyp errors

While attempting to get the Forge Responsive Connected Database to build. I am unable to build this application on my Windows 10 machine. I am unable to succesffuly run “npm install”. I get the following errors as listed below. I ended up trying to use a pre-configured “canvas” and it still didn’t let the node app run.

I have tried these solutions to no success:

1 Answer 1

Here are the full installation and setup steps I tested on two different 2 different computers with Windows10 installed.

Pre-Installations:

Node.js global packages:

Visual Studio 2017 (link):

GTK with cairo library (link):

Main Installations:

Configurations:

Open configdevelopment.config.js with your editor and change values of viewer section into:

Change the database section in the configdevelopment.config.js with you MongoDB connection settings.

Restore dummy database data in the resources/db/dev or resources/db/prod via Mongochef’s Import function.

Open Powershell normally(say current user) and set following environment variables:

Run the project

Change current directory of the Powershell into the source code folder of the forge-rcdb and type npm start

open http://localhost:3000 in your favorite browser.

Trouble Shooting

If you see the response of http://localhost:3000/api/forge/user showing HTTP EORROR CODE 404 from the browser dev console, then you must have to check whether the CallBack URL of your Forge App used to host forge-rcdb in Forge Dev Protal is http://localhost:3000/api/forge/callback/oauth. (note. This config can be changed in configdevelopment.config.js )

If you cannot load any listed models from the web pages, it means there is not downloaded viewable bubbles in your resourcesmodelsprod or resourcesmodelsdev as well as your Forge OSS bucket. So, please check the urn value in your database whether you have those models in these positions previously mentioned.

If you found the main reason for item 3 of Trouble Shooting is that you didn’t own models listed in the forge-rcdb, that’s because these models are Autodesk’s private models or uploaded by other users themselves before, that might not be shared to the public, unfortunately. To fix this issue, you have to change the example data of MongoDB Collections mentioned in step 3 of the configuration section to your own models.

Источник

node-gyp build error windows x64

Here’s what I’ve done so far on my x64 OS:

Successfully executed node-gyp configure (from my add-on directory under nodejsnode_modules where binding.gyp is located)

ran node-gyp build (as administrator)** This is what crashed, leaving me with:

LINK : fatal error LNK1181: cannot open input file ‘kernel32.lib’ [C:Program Filesnodejsnode_modulesmsnodesqlbuildsqlserver.vcxproj]

Any ideas as to what is going on? Thanks in advance! Just trying to use my node-sqlserver MS driver for Node.js

11 Answers 11

I had a similar problem. I found that this switch helped me

After spending a while to get this to work (for me accepted answer didn’t work, for me it’s just half solution) i did following:

Sadly, you must have visual studio (i installed express edition 2013 for DESKTOP)

Installed python 2.7.3 (you don’t have to set any environment variables)

Run cmd as administrator and go to you project root (where is you package.json file)

First run: npm config set python C:Python27python.exe

Delete C:Usersuser_name.node-gyp

Delete %AppData%/npm

Delete %AppData%/npm-cache

And install node-gyp again

Following instruction on node-gyp page

For installing node-gyp in windows or any other OS

First you may have to download the node-gyp by

you may need to do the above procedure as root/administrartor.

I had this same error now in 2015 when trying to install Keystone and I ran through all you told me but it didn’t work on it’s own. At the end, I just had to run the command

Источник

[Win 10 GPU] Error: node-gyp rebuild failed with: Error: Command failed: node-gyp rebuild #445

Getting error while intalling GPU version of tensorflow.js (npm install @tensorflow/tfjs-node-gpu) I have followed below links

We already have setup below:

We have followed almost all the articles and installed all the dependencies but still facing the issue.

Complete Error info:

preinstall: @tensorflow/tfjs-node-gpu@1.0.2 55 timing action:preinstall Completed in 5ms 56 silly doSerial build 8 57 silly build @tensorflow/tfjs-node-gpu@1.0.2 58 info linkStuff @tensorflow/tfjs-node-gpu@1.0.2 59 silly linkStuff @tensorflow/tfjs-node-gpu@1.0.2 has C:prndtfjs-nodenode_modules as its parent node_modules 60 timing action:build Completed in 3ms 61 silly doSerial global-link 8 62 silly doParallel update-linked 0 63 silly doSerial install 8 64 silly install @tensorflow/tfjs-node-gpu@1.0.2 65 info lifecycle @tensorflow/tfjs-node-gpu@1.0.2

install: @tensorflow/tfjs-node-gpu@1.0.2 66 verbose lifecycle @tensorflow/tfjs-node-gpu@1.0.2

install: unsafe-perm in lifecycle true 67 verbose lifecycle @tensorflow/tfjs-node-gpu@1.0.2

install: PATH: C:UsersPRNDAppDataRoamingnpmnode_modulesnpmnode_modulesnpm-lifecyclenode-gyp-bin;C:prndtfjs-nodenode_modules@tensorflowtfjs-node-gpunode_modules.bin;C:prndtfjs-nodenode_modules.bin;C:Program Files (x86)IntelIntel(R) Management Engine ComponentsiCLS;C:Program FilesIntelIntel(R) Management Engine ComponentsiCLS;C:Windowssystem32;C:Windows;C:WindowsSystem32Wbem;C:WindowsSystem32WindowsPowerShellv1.0;C:Program Files (x86)IntelIntel(R) Management Engine ComponentsDAL;C:Program FilesIntelIntel(R) Management Engine ComponentsDAL;C:Program FilesNVIDIA CorporationNVIDIA NGX;C:Program Files (x86)NVIDIA CorporationPhysXCommon;C:nodejs;C:Program Filesdotnet;C:Program FilesGitcmd;C:nodejs;C:Python27;C:Program Files (x86)MSBuild14.0Bin;C:Python27;C:UsersPRNDAppDataRoamingnpmnode_modulesnpmnode_modulesnpm-lifecyclenode-gyp-bin;C:UsersPRNDAppDataRoamingnpmnode_moduleswindows-build-toolsnode_modules.bin;C:UsersPRNDAppDataRoamingnpmnode_modules.bin;C:UsersPRNDAppDataLocalProgramsPythonPython37-32;C:UsersPRNDAppDataLocalProgramsPythonPython37-32;C:Program Files (x86)Yarnbin;C:Program Filesnodejs;C:Python27;C:UsersPRNDAppDataRoamingnpmnode_modulesnpmnode_modulesnpm-lifecyclenode-gyp-bin;C:UsersPRNDAppDataRoamingnpmnode_moduleswindows-build-toolsnode_modules.bin;C:UsersPRNDAppDataRoamingnpmnode_modules.bin;C:Python27;C:UsersPRNDAppDataRoamingnpmnode_modulesnpmnode_modulesnpm-lifecyclenode-gyp-bin;C:Windowssystem32node_moduleswindows-build-toolsnode_modules.bin;C:Windowssystem32node_modules.bin;C:Python27;C:UsersPRNDAppDataRoamingnpmnode_modulesnpmnode_modulesnpm-lifecyclenode-gyp-bin;C:UsersPRNDAppDataRoamingnpmnode_moduleswindows-build-toolsnode_modules.bin;C:UsersPRNDAppDataRoamingnpmnode_modules.bin;C:UsersPRNDAppDataLocalMicrosoftWindowsApps;C:UsersPRNDAppDataRoamingnpm 68 verbose lifecycle @tensorflow/tfjs-node-gpu@1.0.2

install: CWD: C:prndtfjs-nodenode_modules@tensorflowtfjs-node-gpu 69 silly lifecycle @tensorflow/tfjs-node-gpu@1.0.2

install: Args: [ ‘/d /s /c’, ‘node scripts/install.js gpu download’ ] 70 timing audit submit Completed in 446ms 71 http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/audits/quick 446ms 72 timing audit body Completed in 1ms 73 silly lifecycle @tensorflow/tfjs-node-gpu@1.0.2

install: Returned: code: 1 signal: null 74 info lifecycle @tensorflow/tfjs-node-gpu@1.0.2

install: Failed to exec install script 75 timing action:install Completed in 57910ms 76 verbose unlock done using C:UsersPRNDAppDataRoamingnpm-cache_locksstaging-1a89f0fd18cf3e22.lock for C:prndtfjs-nodenode_modules.staging 77 timing stage:rollbackFailedOptional Completed in 182ms 78 timing stage:runTopLevelLifecycles Completed in 60404ms 79 silly saveTree @tensorflow/tfjs-node@1.0.2 79 silly saveTree +— @tensorflow/tfjs-node-gpu@1.0.2 79 silly saveTree | +— @tensorflow/tfjs@1.0.3 79 silly saveTree | | +— @tensorflow/tfjs-converter@1.0.3 79 silly saveTree | | +— @tensorflow/tfjs-core@1.0.3 79 silly saveTree | | | +— @types/seedrandom@2.4.27 79 silly saveTree | | | +— @types/webgl-ext@0.0.30 79 silly saveTree | | | +— @types/webgl2@0.0.4 79 silly saveTree | | | `— seedrandom@2.4.3 79 silly saveTree | | +— @tensorflow/tfjs-data@1.0.3 79 silly saveTree | | | +— @types/node-fetch@2.1.7 79 silly saveTree | | | | `— @types/node@11.12.2 79 silly saveTree | | | `— node-fetch@2.1.2 79 silly saveTree | | `— @tensorflow/tfjs-layers@1.0.3 79 silly saveTree | +— adm-zip@0.4.13 79 silly saveTree | +— bindings@1.3.1 79 silly saveTree | +— https-proxy-agent@2.2.1 79 silly saveTree | | +— agent-base@4.2.1 79 silly saveTree | | | `— es6-promisify@5.0.0 79 silly saveTree | | | `— es6-promise@4.2.6 79 silly saveTree | | `— debug@3.2.6 79 silly saveTree | | `— ms@2.1.1 79 silly saveTree | +— node-fetch@2.3.0 79 silly saveTree | +— progress@2.0.3 79 silly saveTree | +— rimraf@2.6.3 79 silly saveTree | | `— glob@7.1.3 79 silly saveTree | | +— fs.realpath@1.0.0 79 silly saveTree | | +— inflight@1.0.6 79 silly saveTree | | | +— once@1.4.0 79 silly saveTree | | | | `— wrappy@1.0.2 79 silly saveTree | | | `— wrappy@1.0.2 79 silly saveTree | | +— inherits@2.0.3 79 silly saveTree | | +— minimatch@3.0.4 79 silly saveTree | | | `— brace-expansion@1.1.11 79 silly saveTree | | | +— balanced-match@1.0.0 79 silly saveTree | | | `— concat-map@0.0.1 79 silly saveTree | | +— once@1.4.0 79 silly saveTree | | `— path-is-absolute@1.0.1 79 silly saveTree | `— tar@4.4.8 79 silly saveTree | +— chownr@1.1.1 79 silly saveTree | +— fs-minipass@1.2.5 79 silly saveTree | | `— minipass@2.3.5 79 silly saveTree | | +— safe-buffer@5.1.2 79 silly saveTree | | `— yallist@3.0.3 79 silly saveTree | +— minipass@2.3.5 79 silly saveTree | +— minizlib@1.2.1 79 silly saveTree | +— mkdirp@0.5.1 79 silly saveTree | | `— minimist@0.0.8 79 silly saveTree | +— safe-buffer@5.1.2 79 silly saveTree | `— yallist@3.0.3 79 silly saveTree +— @tensorflow/tfjs@1.0.3 79 silly saveTree +— @types/bindings@1.3.0 79 silly saveTree +— @types/jasmine@2.8.16 79 silly saveTree +— @types/node@10.14.4 79 silly saveTree +— @types/progress@2.0.3 79 silly saveTree +— @types/rimraf@2.0.2 79 silly saveTree | `— @types/glob@7.1.1 79 silly saveTree | +— @types/events@3.0.0 79 silly saveTree | `— @types/minimatch@3.0.3 79 silly saveTree +— adm-zip@0.4.13 79 silly saveTree +— aws-sdk@2.432.0 79 silly saveTree | +— buffer@4.9.1 79 silly saveTree | | +— base64-js@1.3.0 79 silly saveTree | | +— ieee754@1.1.8 79 silly saveTree | | `— isarray@1.0.0 79 silly saveTree | +— events@1.1.1 79 silly saveTree | +— ieee754@1.1.8 79 silly saveTree | +— jmespath@0.15.0 79 silly saveTree | +— querystring@0.2.0 79 silly saveTree | +— sax@1.2.1 79 silly saveTree | +— url@0.10.3 79 silly saveTree | | `— punycode@1.3.2 79 silly saveTree | +— uuid@3.3.2 79 silly saveTree | `— xml2js@0.4.19 79 silly saveTree | `— xmlbuilder@9.0.7 79 silly saveTree +— bindings@1.3.1 79 silly saveTree +— clang-format@1.2.4 79 silly saveTree | +— async@1.5.2 79 silly saveTree | `— resolve@1.10.0 79 silly saveTree | `— path-parse@1.0.6 79 silly saveTree +— https-proxy-agent@2.2.1 79 silly saveTree +— jasmine@3.1.0 79 silly saveTree | `— jasmine-core@3.1.0 79 silly saveTree +— node-fetch@2.3.0 79 silly saveTree +— nyc@13.3.0 79 silly saveTree | +— archy@1.0.0 79 silly saveTree | +— arrify@1.0.1 79 silly saveTree | +— caching-transform@3.0.1 79 silly saveTree | | +— hasha@3.0.0 79 silly saveTree | | | `— is-stream@1.1.0 79 silly saveTree | | +— make-dir@1.3.0 79 silly saveTree | | | `— pify@3.0.0 79 silly saveTree | | +— package-hash@3.0.0 79 silly saveTree | | | +— graceful-fs@4.1.15 79 silly saveTree | | | +— lodash.flattendeep@4.4.0 79 silly saveTree | | | `— release-zalgo@1.0.0 79 silly saveTree | | | `— es6-error@4.1.1 79 silly saveTree | | `— write-file-atomic@2.4.2 79 silly saveTree | | +— imurmurhash@0.1.4 79 silly saveTree | | `— signal-exit@3.0.2 79 silly saveTree | +— convert-source-map@1.6.0 79 silly saveTree | | `— safe-buffer@5.1.2 79 silly saveTree | +— find-cache-dir@2.0.0 79 silly saveTree | | +— commondir@1.0.1 79 silly saveTree | | `— pkg-dir@3.0.0 79 silly saveTree | | `— find-up@3.0.0 79 silly saveTree | | `— locate-path@3.0.0 79 silly saveTree | | +— p-locate@3.0.0 79 silly saveTree | | | `— p-limit@2.1.0 79 silly saveTree | | | `— p-try@2.0.0 79 silly saveTree | | `— path-exists@3.0.0 79 silly saveTree | +— find-up@3.0.0 79 silly saveTree | +— foreground-child@1.5.6 79 silly saveTree | | `— cross-spawn@4.0.2 79 silly saveTree | | +— lru-cache@4.1.5 79 silly saveTree | | | +— pseudomap@1.0.2 79 silly saveTree | | | `— yallist@2.1.2 79 silly saveTree | | `— which@1.3.1 79 silly saveTree | | `— isexe@2.0.0 79 silly saveTree | +— glob@7.1.3 79 silly saveTree | | +— fs.realpath@1.0.0 79 silly saveTree | | +— inflight@1.0.6 79 silly saveTree | | | +— once@1.4.0 79 silly saveTree | | | | `— wrappy@1.0.2 79 silly saveTree | | | `— wrappy@1.0.2 79 silly saveTree | | +— inherits@2.0.3 79 silly saveTree | | +— minimatch@3.0.4 79 silly saveTree | | | `— brace-expansion@1.1.11 79 silly saveTree | | | +— balanced-match@1.0.0 79 silly saveTree | | | `— concat-map@0.0.1 79 silly saveTree | | +— once@1.4.0 79 silly saveTree | | `— path-is-absolute@1.0.1 79 silly saveTree | +— istanbul-lib-coverage@2.0.3 79 silly saveTree | +— istanbul-lib-hook@2.0.3 79 silly saveTree | | `— append-transform@1.0.0 79 silly saveTree | | `— default-require-extensions@2.0.0 79 silly saveTree | | `— strip-bom@3.0.0 79 silly saveTree | +— istanbul-lib-instrument@3.1.0 79 silly saveTree | | +— @babel/generator@7.4.0 79 silly saveTree | | | +— @babel/types@7.4.0 79 silly saveTree | | | | +— esutils@2.0.2 79 silly saveTree | | | | +— lodash@4.17.11 79 silly saveTree | | | | `— to-fast-properties@2.0.0 79 silly saveTree | | | +— jsesc@2.5.2 79 silly saveTree | | | +— lodash@4.17.11 79 silly saveTree | | | +— source-map@0.5.7 79 silly saveTree | | | `— trim-right@1.0.1 79 silly saveTree | | +— @babel/parser@7.4.2 79 silly saveTree | | +— @babel/template@7.4.0 79 silly saveTree | | | `— @babel/code-frame@7.0.0 79 silly saveTree | | | `— @babel/highlight@7.0.0 79 silly saveTree | | | +— chalk@2.4.2 79 silly saveTree | | | | +— ansi-styles@3.2.1 79 silly saveTree | | | | | `— color-convert@1.9.3 79 silly saveTree | | | | | `— color-name@1.1.3 79 silly saveTree | | | | +— escape-string-regexp@1.0.5 79 silly saveTree | | | | `— supports-color@5.5.0 79 silly saveTree | | | | `— has-flag@3.0.0 79 silly saveTree | | | `— js-tokens@4.0.0 79 silly saveTree | | +— @babel/traverse@7.4.0 79 silly saveTree | | | +— @babel/helper-function-name@7.1.0 79 silly saveTree | | | | `— @babel/helper-get-function-arity@7.0.0 79 silly saveTree | | | +— @babel/helper-split-export-declaration@7.4.0 79 silly saveTree | | | +— debug@4.1.1 79 silly saveTree | | | `— globals@11.11.0 79 silly saveTree | | +— @babel/types@7.4.0 79 silly saveTree | | +— istanbul-lib-coverage@2.0.3 79 silly saveTree | | `— semver@5.7.0 79 silly saveTree | +— istanbul-lib-report@2.0.4 79 silly saveTree | | `— supports-color@6.1.0 79 silly saveTree | | `— has-flag@3.0.0 79 silly saveTree | +— istanbul-lib-source-maps@3.0.2 79 silly saveTree | | +— debug@4.1.1 79 silly saveTree | | | `— ms@2.1.1 79 silly saveTree | | +— rimraf@2.6.3 79 silly saveTree | | `— source-map@0.6.1 79 silly saveTree | +— istanbul-reports@2.1.1 79 silly saveTree | | `— handlebars@4.1.0 79 silly saveTree | | +— async@2.6.2 79 silly saveTree | | | `— lodash@4.17.11 79 silly saveTree | | +— optimist@0.6.1 79 silly saveTree | | | +— minimist@0.0.10 79 silly saveTree | | | `— wordwrap@0.0.3 79 silly saveTree | | +— source-map@0.6.1 79 silly saveTree | | `— uglify-js@3.4.9 79 silly saveTree | | +— commander@2.17.1 79 silly saveTree | | `— source-map@0.6.1 79 silly saveTree | +— make-dir@1.3.0 79 silly saveTree | +— merge-source-map@1.1.0 79 silly saveTree | | `— source-map@0.6.1 79 silly saveTree | +— resolve-from@4.0.0 79 silly saveTree | +— rimraf@2.6.3 79 silly saveTree | +— signal-exit@3.0.2 79 silly saveTree | +— spawn-wrap@1.4.2 79 silly saveTree | | +— mkdirp@0.5.1 79 silly saveTree | | | `— minimist@0.0.8 79 silly saveTree | | `— os-homedir@1.0.2 79 silly saveTree | +— test-exclude@5.1.0 79 silly saveTree | | +— read-pkg-up@4.0.0 79 silly saveTree | | | `— read-pkg@3.0.0 79 silly saveTree | | | +— load-json-file@4.0.0 79 silly saveTree | | | | `— parse-json@4.0.0 79 silly saveTree | | | | +— error-ex@1.3.2 79 silly saveTree | | | | | `— is-arrayish@0.2.1 79 silly saveTree | | | | `— json-parse-better-errors@1.0.2 79 silly saveTree | | | +— normalize-package-data@2.5.0 79 silly saveTree | | | | +— hosted-git-info@2.7.1 79 silly saveTree | | | | +— resolve@1.10.0 79 silly saveTree | | | | | `— path-parse@1.0.6 79 silly saveTree | | | | +— semver@5.6.0 79 silly saveTree | | | | `— validate-npm-package-license@3.0.4 79 silly saveTree | | | | +— spdx-correct@3.1.0 79 silly saveTree | | | | | +— spdx-expression-parse@3.0.0 79 silly saveTree | | | | | | +— spdx-exceptions@2.2.0 79 silly saveTree | | | | | | `— spdx-license-ids@3.0.3 79 silly saveTree | | | | | `— spdx-license-ids@3.0.3 79 silly saveTree | | | | `— spdx-expression-parse@3.0.0 79 silly saveTree | | | `— path-type@3.0.0 79 silly saveTree | | `— require-main-filename@1.0.1 79 silly saveTree | +— uuid@3.3.2 79 silly saveTree | +— yargs-parser@11.1.1 79 silly saveTree | | +— camelcase@5.0.0 79 silly saveTree | | `— decamelize@1.2.0 79 silly saveTree | `— yargs@12.0.5 79 silly saveTree | +— cliui@4.1.0 79 silly saveTree | | +— string-width@2.1.1 79 silly saveTree | | | +— is-fullwidth-code-point@2.0.0 79 silly saveTree | | | `— strip-ansi@4.0.0 79 silly saveTree | | | `— ansi-regex@3.0.0 79 silly saveTree | | +— strip-ansi@4.0.0 79 silly saveTree | | `— wrap-ansi@2.1.0 79 silly saveTree | | +— string-width@1.0.2 79 silly saveTree | | | +— code-point-at@1.1.0 79 silly saveTree | | | +— is-fullwidth-code-point@1.0.0 79 silly saveTree | | | | `— number-is-nan@1.0.1 79 silly saveTree | | | `— strip-ansi@3.0.1 79 silly saveTree | | | `— ansi-regex@2.1.1 79 silly saveTree | | `— strip-ansi@3.0.1 79 silly saveTree | +— get-caller-file@1.0.3 79 silly saveTree | +— os-locale@3.1.0 79 silly saveTree | | +— execa@1.0.0 79 silly saveTree | | | +— cross-spawn@6.0.5 79 silly saveTree | | | | +— nice-try@1.0.5 79 silly saveTree | | | | +— path-key@2.0.1 79 silly saveTree | | | | `— shebang-command@1.2.0 79 silly saveTree | | | | `— shebang-regex@1.0.0 79 silly saveTree | | | +— get-stream@4.1.0 79 silly saveTree | | | | `— pump@3.0.0 79 silly saveTree | | | | `— end-of-stream@1.4.1 79 silly saveTree | | | +— npm-run-path@2.0.2 79 silly saveTree | | | +— p-finally@1.0.0 79 silly saveTree | | | `— strip-eof@1.0.0 79 silly saveTree | | +— lcid@2.0.0 79 silly saveTree | | | `— invert-kv@2.0.0 79 silly saveTree | | `— mem@4.1.0 79 silly saveTree | | +— map-age-cleaner@0.1.3 79 silly saveTree | | | `— p-defer@1.0.0 79 silly saveTree | | +— mimic-fn@1.2.0 79 silly saveTree | | `— p-is-promise@2.0.0 79 silly saveTree | +— require-directory@2.1.1 79 silly saveTree | +— set-blocking@2.0.0 79 silly saveTree | +— string-width@2.1.1 79 silly saveTree | +— which-module@2.0.0 79 silly saveTree | `— y18n@4.0.0 79 silly saveTree +— progress@2.0.3 79 silly saveTree +— rimraf@2.6.3 79 silly saveTree +— shelljs@0.8.3 79 silly saveTree | +— interpret@1.2.0 79 silly saveTree | `— rechoir@0.6.2 79 silly saveTree +— tar@4.4.8 79 silly saveTree +— tmp@0.0.33 79 silly saveTree | `— os-tmpdir@1.0.2 79 silly saveTree +— ts-node@5.0.1 79 silly saveTree | +— arrify@1.0.1 79 silly saveTree | +— diff@3.5.0 79 silly saveTree | +— make-error@1.3.5 79 silly saveTree | +— minimist@1.2.0 79 silly saveTree | +— source-map-support@0.5.11 79 silly saveTree | | +— buffer-from@1.1.1 79 silly saveTree | | `— source-map@0.6.1 79 silly saveTree | `— yn@2.0.0 79 silly saveTree +— tslint@5.9.1 79 silly saveTree | +— babel-code-frame@6.26.0 79 silly saveTree | | +— chalk@1.1.3 79 silly saveTree | | | +— ansi-styles@2.2.1 79 silly saveTree | | | +— has-ansi@2.0.0 79 silly saveTree | | | | `— ansi-regex@2.1.1 79 silly saveTree | | | +— strip-ansi@3.0.1 79 silly saveTree | | | `— supports-color@2.0.0 79 silly saveTree | | `— js-tokens@3.0.2 79 silly saveTree | +— builtin-modules@1.1.1 79 silly saveTree | +— commander@2.19.0 79 silly saveTree | +— js-yaml@3.13.0 79 silly saveTree | | +— argparse@1.0.10 79 silly saveTree | | | `— sprintf-js@1.0.3 79 silly saveTree | | `— esprima@4.0.1 79 silly saveTree | +— tslib@1.9.3 79 silly saveTree | `— tsutils@2.29.0 79 silly saveTree +— typescript@3.3.3333 79 silly saveTree `— yalc@1.0.0-pre.27 79 silly saveTree +— del@2.2.2 79 silly saveTree | +— globby@5.0.0 79 silly saveTree | | +— array-union@1.0.2 79 silly saveTree | | | `— array-uniq@1.0.3 79 silly saveTree | | +— object-assign@4.1.1 79 silly saveTree | | +— pify@2.3.0 79 silly saveTree | | `— pinkie-promise@2.0.1 79 silly saveTree | | `— pinkie@2.0.4 79 silly saveTree | +— is-path-cwd@1.0.0 79 silly saveTree | +— is-path-in-cwd@1.0.1 79 silly saveTree | | `— is-path-inside@1.0.1 79 silly saveTree | | `— path-is-inside@1.0.2 79 silly saveTree | +— object-assign@4.1.1 79 silly saveTree | +— pify@2.3.0 79 silly saveTree | `— pinkie-promise@2.0.1 79 silly saveTree +— fs-extra@4.0.3 79 silly saveTree | +— graceful-fs@4.1.15 79 silly saveTree | +— jsonfile@4.0.0 79 silly saveTree | `— universalify@0.1.2 79 silly saveTree +— graceful-fs@4.1.15 79 silly saveTree +— ignore@5.0.6 79 silly saveTree +— npm-packlist-fixed@1.1.12 79 silly saveTree | +— ignore-walk@3.0.1 79 silly saveTree | `— npm-bundled@1.0.6 79 silly saveTree +— user-home@2.0.0 79 silly saveTree | `— os-homedir@1.0.2 79 silly saveTree `— yargs@7.1.0 79 silly saveTree +— camelcase@3.0.0 79 silly saveTree +— cliui@3.2.0 79 silly saveTree | +— string-width@1.0.2 79 silly saveTree | | +— code-point-at@1.1.0 79 silly saveTree | | `— is-fullwidth-code-point@1.0.0 79 silly saveTree | | `— number-is-nan@1.0.1 79 silly saveTree | `— wrap-ansi@2.1.0 79 silly saveTree +— decamelize@1.2.0 79 silly saveTree +— get-caller-file@1.0.3 79 silly saveTree +— os-locale@1.4.0 79 silly saveTree | `— lcid@1.0.0 79 silly saveTree | `— invert-kv@1.0.0 79 silly saveTree +— read-pkg-up@1.0.1 79 silly saveTree | +— find-up@1.1.2 79 silly saveTree | | `— path-exists@2.1.0 79 silly saveTree | `— read-pkg@1.1.0 79 silly saveTree | +— load-json-file@1.1.0 79 silly saveTree | | +— parse-json@2.2.0 79 silly saveTree | | | `— error-ex@1.3.2 79 silly saveTree | | | `— is-arrayish@0.2.1 79 silly saveTree | | `— strip-bom@2.0.0 79 silly saveTree | | `— is-utf8@0.2.1 79 silly saveTree | +— normalize-package-data@2.5.0 79 silly saveTree | | +— hosted-git-info@2.7.1 79 silly saveTree | | `— validate-npm-package-license@3.0.4 79 silly saveTree | | +— spdx-correct@3.1.0 79 silly saveTree | | | +— spdx-expression-parse@3.0.0 79 silly saveTree | | | | +— spdx-exceptions@2.2.0 79 silly saveTree | | | | `— spdx-license-ids@3.0.3 79 silly saveTree | | | `— spdx-license-ids@3.0.3 79 silly saveTree | | `— spdx-expression-parse@3.0.0 79 silly saveTree | `— path-type@1.1.0 79 silly saveTree +— require-directory@2.1.1 79 silly saveTree +— require-main-filename@1.0.1 79 silly saveTree +— set-blocking@2.0.0 79 silly saveTree +— string-width@1.0.2 79 silly saveTree +— which-module@1.0.0 79 silly saveTree +— y18n@3.2.1 79 silly saveTree `— yargs-parser@5.0.0 80 warn @tensorflow/tfjs-node@1.0.2 No license field. 81 verbose stack Error: @tensorflow/tfjs-node-gpu@1.0.2 install: `node scripts/install.js gpu download` 81 verbose stack Exit status 1 81 verbose stack at EventEmitter. (C:UsersPRNDAppDataRoamingnpmnode_modulesnpmnode_modulesnpm-lifecycleindex.js:301:16) 81 verbose stack at EventEmitter.emit (events.js:193:13) 81 verbose stack at ChildProcess. (C:UsersPRNDAppDataRoamingnpmnode_modulesnpmnode_modulesnpm-lifecyclelibspawn.js:55:14) 81 verbose stack at ChildProcess.emit (events.js:193:13) 81 verbose stack at maybeClose (internal/child_process.js:1001:16) 81 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:266:5) 82 verbose pkgid @tensorflow/tfjs-node-gpu@1.0.2 83 verbose cwd C:prndtfjs-node 84 verbose Windows_NT 10.0.16299 85 verbose argv «C:\nodejs\node.exe» «C:\Users\PRND\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js» «install» «@tensorflow/tfjs-node-gpu» 86 verbose node v11.13.0 87 verbose npm v6.9.0 88 error code ELIFECYCLE 89 error errno 1 90 error @tensorflow/tfjs-node-gpu@1.0.2 install: `node scripts/install.js gpu download` 90 error Exit status 1 91 error Failed at the @tensorflow/tfjs-node-gpu@1.0.2 install script. 91 error This is probably not a problem with npm. There is likely additional logging output above. 92 verbose exit [ 1, true ] «>

The text was updated successfully, but these errors were encountered:

Источник

node-gyp is a tool that enables the compilation of native add-on modules for Node in multiple platforms. It has widespread use and is included as a dependency in many NPM packages.

On most systems, this isn’t an issue, and installing node-gyp with the rest of your packages works as expected. Unfortunately, this is not the case with Windows, as is evidenced by this thread from 2015. The Windows environment makes getting node-gyp to work a less-than-stellar developer experience, full of multiple pitfalls and many ways for things to go wrong.

This guide is meant to help solve the issues that can arise when installing a package that requires node-gyp.

1. Try running npm install with the --no-optional flag.

If you’re lucky, the dependency that requires node-gyp will be optional, and you can skip the entire process required to get it working. Try running npm install –no-optional to install only the required dependencies.

If you run this and still get the error, I have bad news: You’re in for a bit of a ride. As we begin our journey into getting node-gyp up and running, here’s an important note for all of the steps that follow. Make sure that you’re always working in an elevated terminal (with administrator privileges) and that you restart your console whenever a download is complete.

2. Try downloading the windows-build-tools package.

According to the node-gyp documentation, this step should be the end-all-be-all solution to fixing node-gyp problems. For most people, that’s true. NPM has a package called windows-build-tools that should automatically install everything you need to get node-gyp working, including the Microsoft build tools, compilers, Python, and everything else required to build native Node modules on Windows.

The good news is that installing this package should take care of all of the wiring up of these components. The bad news is that there are a lot of things included in it.

Depending on the version you download, it can hover between three and eight gigabytes (all to get some dependencies installed!). The install can take upwards of 30 minutes depending on your connection, so don’t despair if it seems like the install is hanging for a while.

You can download them by running this command: npm install --global --production windows-build-tools --vs2015

Important note

If you run this command without any additional flags, you’ll install the files associated with the latest version of Visual Studio, which is VS2017 at the time of writing. However, node-gyp requires the v140 distributable, not the v150 (which comes with VS2017). This is why the --vs2015 flag is added to the end of the command, since that’s the last version of Visual Studio that came with the v140 package. You can see more notes about that near the bottom of the package’s website.

Hopefully, that’s all it will take for you to get everything installed. If you’ve still got issues, then you’re going to have to grab all of the required files manually.

3. Download the Visual Studio 2015 build tools manually.

Rather than installing the build tools through NPM, download them manually. You can find them on the Microsoft download page. Once they’re downloaded, just run the installer.

4. Tell Node to use the 2015 build tools.

Now that we have the build tools, we need to tell Node to use them. You’ll have to run this command: npm config set msvs_version 2015 –global

5. Make sure you have Python 2.7 installed.

Next up is to download Python 2.7. This is important–by default, you’ll install the newest version (3.x.x), but only 2.7 is compatible with node-gyp. If you try to use a newer version of Python, you’ll get a syntax error due to print being made into an actual function in Python 3.

If you have another version of Python already installed, that’s okay. They can coexist with each other. You can grab Python 2.7 at this link.

6. Set your Node config to use Python 2.7.

Now that you have Python 2.7, you’re going to have to set Node to use it by default. To do that, run this command: npm config set python python2.7

If you followed the last few steps, you should now have everything necessary to get node-gyp working. Make sure you’ve restarted your terminal and are running it as an administrator, and try doing your install again. Hopefully, at this point, you can successfully install the dependencies you need. If not, we’re going to have to try one last thing.

7. Repeat Step 2 with the Visual Studio 2017 build tools.

I’ve personally had issues when I’ve tried to download the 2017 version of the build tools, even when trying to use newer versions of node-gyp. If you look online, you’ll see lots of other people with the same problem, including some of the commenters on this StackOverflow question.

However, most of the documentation around node-gyp and compiling native Node modules on Windows doesn’t specify to use the --vs2015 flag, and some even mention downloading the 2017 version. If you’re still having issues with getting node-gyp to run, try repeating Step 2 while omitting the --vs2015 flag.

8. Try installing an older version of Node.

Still getting an installation error? Try installing an older version of Node. If you’re on an experimental version, try going back to the last stable release (and then make sure that you’re actually using that version when you try and do npm install).

If that still doesn’t work, try going back to Node 8. You’ll find some issues online of people having issues with Node 10 that were resolved by downgrading to Node 8, and sometimes newer versions of Node don’t play nice with node-gyp.

9. File an issue.

If you’re still having trouble getting node-gyp to work, then your issue probably doesn’t fall into one of the more common problems. It’s worth doing some research online to see if that solves your problem. Otherwise, your best option is to file an issue on the GitHub page for node-gyp and see what advice you can get there.

Other Resources

Much of this information can now be found on the GitHub readme for node-gyp, but it wasn’t always there. It only made an appearance after a few thousand posts from disgruntled Windows users who just wanted to install some dependencies. Even then, the information is missing some of the issues that arise with installing the wrong version of the build tools.

Another great resource is Microsoft’s guide on working with Node on Windows. It even has sections dedicated to compiling native Node modules and resolving basic node-gyp problems.

Additionally, this question on StackOverflow contains useful answers and comments regarding this issue. Leave a note in the comments if you’ve found anything else helpful in solving node-gyp issues!

I hit this problem once or twice a year and always seem to forget how easy it is to fix the problem. This blog post will ensure that not only I remember, but the entire Internet will remember the solution I use.

Here goes.

The Problem

The problem is simple: You pull down a repository that uses NPM for package management onto your Windows machine, you type npm install and you get something like this:

1

npm ERR! Failed at the <package>@<version> install script 'node-gyp rebuild'

or

1

gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.

This is because the project you’re trying to build requires the node-gyp package to build something natively on the platform. That package required Python 2.7 and a few other pieces too.

The Solution

Simple problems sometimes get simple solutions.

Thanks to the node-gyp team, that is the case and they have documented it in the project README.

Using a PowerShell CLI instance with administrative priviledges, and use the following code:

1

npm install --global --production windows-build-tools

And that’s it.

There is a manual option as well, but I haven’t needed to use it as the first option always works for me.

Recently, when attempting to install the gulp package using the npm CLI (“Node package manager”, “Command line interface”) in the Terminal app, I saw an error message saying that node-gyp rebuild is failed because no Xcode or CLT version detected. In this tutorial, you’ll learn how to solve this problem.

What causes this error

In my case, the below error appeared when attempting to install the gulp package using the npm CLI (“Node package manager”, “Command line interface”) in the Terminal app.

$ npm install -g gulp
/usr/local/bin/gulp -> /usr/local/lib/node_modules/gulp/bin/gulp.js

> fsevents@1.2.11 install /usr/local/lib/node_modules/gulp/node_modules/fsevents
> node-gyp rebuild

No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.

gyp: No Xcode or CLT version detected!
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack     at ChildProcess.emit (events.js:321:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Darwin 19.3.0
gyp ERR! command "/usr/local/Cellar/node/13.8.0/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/gulp/node_modules/fsevents
gyp ERR! node -v v13.8.0
gyp ERR! node-gyp -v v5.0.7
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/gulp/node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

+ gulp@4.0.2
added 316 packages from 217 contributors in 65.799s

The error message above is self explanatory. It saying that the node-gyp rebuild is failed, and this is because No Xcode or CLT version detected.

• Xcode is an integrated development environment (IDE) for macOS containing a suite of software development tools developed by Apple for developing software for macOS, iPadOS, iOS, watchOS, and tvOS.
• The CLT stands for “Command Line Tools for Xcode”. This package enables UNIX-style development via Terminal by installing command line developer tools, as well as macOS SDK frameworks and headers. Many useful tools are included, such as the Apple LLVM compiler, linker, and Make. If you use Xcode, these tools are also embedded within the Xcode IDE.

This is strange because I am sure that the “Command Line Tools for Xcode” is installed on my Mac; I already used these tools, and before everything was fine. In my case, this error appeared after upgrading macOS to version 10.15 called “Catalina”. Therefore I thought that maybe there is some kind of problem with paths in my “Command Line Tools for Xcode” installation after upgrading macOS to Catalina, and I just need to reinstall the “Command Line Tools for Xcode” on my Mac to solve the problem.

Now we know what caused this error.

How to solve it

Once we know what is causing the node-gyp rebuild to fail, we can use it to solve the problem. It is a really easy process. To solve this problem, we need to manually download and install the macOS “Command Line Tools for Xcode”. Now, step by step guide.

We can get macOS “Command Line Tools for Xcode” from the Developer section of the Apple website. For this, just browse to the developer.apple.com page, find the latest version of the “Command Line Tools for Xcode” and download it to your computer.

Note! At the time of this writing, the latest version of the “Command Line Tools for Xcode” is 11.3.1.

macOS “Command Line Tools for Xcode” (im my case version is 11.3.1) download directly to our Downloads folder as an DMG image file named Command_Line_Tools_for_Xcode_11.3.1.dmg.

• A DMG file is a mountable disk image used to distribute software to the macOS operating system. Today, software developers typically build and distribute applications for macOS as DMG. In other words, DMG files are containers for apps in macOS.

Now we can install the “Command Line Tools for Xcode” using the file downloaded in the previous step. For this, just double-click on the Command_Line_Tools_for_Xcode_11.3.1.dmg file to mount it, then double-click on the Command_Line_Tools.pkg file in the window that opens to launch the installation wizard, and follow the installation wizard instructions.

Finally, we can try to install a package and verify that it installs without the node-gyp rebuild error.

Launch the Terminal app from the Utilities folder of your Applications folder, or use Spotlight to find it.

Type the following command and press the Enter key to install a package (in this example gulp will be installed).

Let the command line do its work and don’t interrupt it until you see the final line that says about how many packages were added and updated. This can take a while, so be patient.

/usr/local/bin/gulp -> /usr/local/lib/node_modules/gulp/bin/gulp.js

> fsevents@1.2.11 install /usr/local/lib/node_modules/gulp/node_modules/fsevents
> node-gyp rebuild

  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
+ gulp@4.0.2
added 71 packages from 33 contributors and updated 1 package in 21.56s

No errors. It works!

Conclusion

That’s it, you’re done. Now the npm should install a packages without the node-gyp rebuild error. So simple isn’t it?

If you are having trouble fixing this problem with the instructions above, but are being able to solve this problem with any another method please describe it in the comment section below. Thanks!

I hope this article has helped you learn how to fix the node-gyp rebuild error. If this article has helped you then please leave a comment

Thanks for reading!