Npm install global windows build tools

Windows-Build-Tools

Please note that the official Node.js for Windows installer can now automatically install the required tools. That’s likely a much better option than the module listed here (windows-build-tools).

On Windows? Want to compile native Node modules? Install the build tools with this one-liner. Start PowerShell as Administrator and run:

npm install --global windows-build-tools

Or, if you are using Yarn:

yarn global add windows-build-tools

Gif

After installation, npm will automatically execute this module, which downloads and installs Visual
C++ Build Tools, provided free of charge for most users by Microsoft (as part of Visual Studio Community, please consult the license to determine whether or not you’re eligible). These tools are required to compile popular native modules.
If not already installed, it will also install Python 3.8, configuring your machine and npm appropriately.

💡 [Windows Vista / 7 only] requires .NET Framework 4.5.1 (Currently not installed automatically by this package)

Both installations are conflict-free, meaning that they do not mess with existing installations of
Visual Studio, C++ Build Tools, or Python. If you see anything that indicates otherwise, please
file a bug.

Visual Studio 2017 vs Visual Studio 2015

This module is capable of installing either the build tools from Visual Studio 2017 or Visual
Studio 2015.

By default, this tool will install the 2017 build tools. To change that, run this script with
the --vs2015 parameter.

Usage

npm [--python-mirror=''] [--proxy=''] [--debug] [--strict-ssl] [--resume] [--sockets=5] [--vcc-build-tools-parameters=''] [--vs2015] [--dry-run-only] install --global windows-build-tools

Optional arguments:

--offline-installers: Path to a folder with already downloaded installers. See
--python-mirror: Use a given mirror to download Python (like --python_mirror=https://npm.taobao.org/mirrors/python/). You can alternatively set a PYTHON_MIRROR environment variable.
--proxy: Use a given proxy. You can alternatively set a PROXY environment variable.
--debug: Be extra verbose in the logger output. Equal to setting the environment variable DEBUG to *.
--strict-ssl: Enables «Strict SSL» mode. Defaults to false.
--resume: By default, windows-build-tools will resume aborted downloads. Set to false to disable.
--sockets: Specifies the number of http sockets to use at once (this controls concurrency). Defaults to infinity.
--vcc-build-tools-parameters: Specifies additional parameters for the Visual C++ Build Tools 2015. See below for more detailed usage instructions.
--silent: The script will not output any information.
--vs2015: Install the Visual Studio 2015 Build Tools instead of the Visual Studio 2017 ones.
--dry-run-only: Don’t actually do anything, just print what the script would have done.
--include-arm64-tools: Include the optional Visual Studio components required to build binaries for ARM64 Windows. Only available with the 2017 and newer build tools and Node.js v12 and up.

Supplying Parameters to the VCC Build Tools

You can pass additional parameters directly to the VCC Build Tools installer. This tool does not
check if the parameters make sense — passing incorrect parameters might break the whole
installation.

Supply parameters to windows-build-tools as a JSON array. Here’s quick example (note the double quotes):

npm --vcc-build-tools-parameters='[""--allWorkloads""]' install --global windows-build-tools

Visual Studio 2015 Parameters

If you run windows-build-tools with --vs2015, these parameters are available:

/AdminFile: Specifies the installation control file.
/CreateAdminFile: Specifies the location to create a control file that can then be used
/CustomInstallPath: Set Custom install location.
/ForceRestart: Always restart the system after installation.
/Full: Install all product features.
/InstallSelectableItems: <item1;item2;…;itemN> Choose which selectable item(s) to be installed.
-selectable item to be installed, just pass in this switch without any value.
/Layout: Create a copy of the media in specified folder.
/NoRefresh: Prevent setup checking for updates from the internet.
/NoRestart: Do not restart during or after installation.
/NoWeb: Prevent setup downloading from the internet.
/Passive: Display progress but do not wait for user input.
/ProductKey: <25-character product key> Set custom product key (no dashes).
/PromptRestart: Prompt the user before restarting the system.
/Repair: Repair the product.
/Uninstall: Uninstall the product.
/Uninstall /Force: Uninstall the product and features shared with other products.

Visual Studio 2017 Parameters

The available parameters are documented here.

Offline Installation

By default, windows-build-tools will download the latest installers from Microsoft each time
it’s installed. Alternatively, you can prepare a folder that contains installers. They need to
have their original names:

Visual Studio Build Tools: vs_BuildTools.exe or BuildTools_Full.exe
Python: python-3.8.1.amd64.msi or python-3.8.1.msi

Then, run windows-build-tools with the --offline-installers argument:

npm install -g windows-build-tools --offline-installers="C:\Users\John\installers"

Support & Help

This package currently only handles the most common use case, none of the edge cases. If you encounter errors, we’d greatly appreciate error reports (and even pull requests). This is currently tested on Windows 10.

Node versions

windows-build-tools 4.0 and up require at least Node v8.
windows-build-tools 3.0 and up require at least Node v6.
windows-build-tools 1.0 and up require at least Node v4.

Where is Python installed?

It’s saved under %USERPROFILE%\.windows-build-tools\python38.

Installing as a Non-Administrator

windows-build-tools works best if installed from an account with administrative rights. However,
thanks to @brucejo75, the following steps can be taken to install to a different user account:

From your non-admin account (e.g. <Me>) run cmd.exe as administrator.
Set the following environment variables in the new command shell:

set APPDATA=C:\Users\<Me>\AppData\Roaming
npm config set prefix C:\Users\<Me>\AppData\Roaming\npm
set USERNAME=<Me>
set USERPROFILE=C:\Users\<Me>

Ensure that the variables passed match your location of npm’s roaming data and the location
of user profiles on your machine. For <me>, substitute the name of the account you want to
install windows-build-tools for. For more information, see the npm config set prefix
description here.

Run npm install -g windows-build-tools

Examples of Modules Supported

In theory, windows-build-tools supports all pure C++ addons for Node.js (and virtually everything
else that requires a native compiler toolchain to be installed on your machine).

To ensure that that’s true, we take a fresh Windows 10 installation, add windows-build-tools, and
ensure that the most popular native Node addons compile from source. Those are: node-sass, bcrypt, sqlite3, serialport, websocket, deasync, grpc, canvas, sharp,
hiredis, leveldown, nodegit, zqm, ffi, libxmljs, iconv, ref, sleep, microtime, couchbase, bignum,
kerberos, and ursa.

License & Credits

The Python installation was made possible by Ali Hajimirza, who kindly wrestled with Python’s MSIs until they surrendered. For details regarding the license agreements applicable to Python, see History and License 3.x.

Use of Microsoft software is subject to the terms of the corresponding license agreements. For details regarding the license agreements applicable to Visual Studio products, refer to their License Directory page. (See also this discussion for the gist of it.)

Copyright (C) 2018 Felix Rieseberg. Licensed MIT. For more details, please see LICENSE.
This license applies to this package only, not to its dependencies or the 3rd party software that it installs.

Источник

Node.js is just JavaScript, right? So it should be really easy to run Node.js applications on Windows—just download and install Node, npm install, and go, right?

Well, for some applications, that’s true. But if you need to compile extensions, you’ll need a few more things. And, of course, with Node.js itself being constantly under development, you’ll want to lock down your development to a version your code can use. In this post, I’ll talk you through how we get our Windows command-line environments set up for the Node.js (actually, Electron) application my team is developing.

First Things First

No one wants to waste time hunting down downloads for a development environment. Instead, install Scoop first, and you’ll get a nice, clean way to add the packages you’ll need without a single web search.

Once you’ve got Scoop installed, it’s time to add some packages. For just Node.js, you’ll want the nodejs package, plus nvm for version management with NVM:

scoop install nodejs nvm

If your project uses Yarn, as ours does, you can grab that from Scoop, as well:

scoop install yarn

If you’re planning on checking out or committing code to GitHub, you’ll also want tools for that:

scoop install openssh git

To finish setting up Git with OpenSSH, note the post-install message that tells you to set up the GIT_SSH environment variable.

Finally, in case you want to quickly do things as an administrative user (which you may, later in this post!), I recommend you install Sudo, which knows how to elevate privileges inside a PowerShell session without spawning a brand new one:

scoop install sudo

Managing Node.js versions

The next thing you’ll want to do is make sure you’re on the right version of Node.js for your project. We’re using the latest LTS version for ours, which as of the time of this writing is 8.11.2. So we issue two NVM commands to install and use it:

nvm install 8.11.2
nvm use 8.11.2

If you’re familiar with NVM on Unix-like systems, you’ll find it works a little differently on Windows with Scoop. When you use a new Node.js version, it will update the binaries under scoop\apps\nvm instead of in $HOME/.nvm.

If you use a version and it doesn’t seem to be taking effect, check your PATH environment variable in the System Properties control panel (search for “environment”); it’s probably been re-ordered. Move the path containing scoop\apps\nvm to the top, and the NVM-selected version will now take precedence.

Compiling Extensions

We don’t have any of our own extensions that need building in our project, but some of our dependencies (namely, node-sass) do.

Extensions like these are built with node-gyp, and node-gyp needs two things: Python (2… wince) and a C compiler, neither of which are standard equipment on a Windows system. If you don’t have them and you need them to build extensions, you will see a long string of gyp ERR! messages when you install dependencies.

Thankfully, there’s a reasonably easy way to install them already configured for node-gyp: windows-build-tools.

After you’ve installed the Scoop nodejs package above, and assuming you installed Sudo, you can now run:

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

Note that we have observed these installers rebooting a system at least once, which effectively aborted the process. We fixed this in this one case by re-running the installer like so:

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

The Moment of Truth

If all the installations worked, you should be ready to go. For our application, a

yarn install
yarn start

was all we needed—of course, you’ll want to start your application however you do normally.

In our case, our application started up and we were off and running. If you have found a more complex case, let me know how you solved it in the comments.

Источник

Windows 10, Node — 8.8.1, NPM — 5.4.2, Node-gyp — 3.6.2

I try to install gemini using: npm install -g gemini

After searching about this issues i was trying to resolve 1 option for Windows in https://github.com/nodejs/node-gyp#on-windows.

And in this flow i have trouble with windows-build-tools installation.
I run in cmd.exe (like Admin) : npm install —global —production windows-build-tools

Console:

C:\Windows\system32>npm install --global --production windows-build-tools

> [email protected] postinstall C:\Users\p.stepanov\AppData\Roaming\npm\node_modules\windows-build-tools
> node ./lib/index.js

Downloading BuildTools_Full.exe
Downloading python-2.7.13.msi
[>                                            ] 0.0% (0 B/s)
Downloaded python-2.7.13.msi. Saved to C:\Users\p.stepanov\.windows-build-tools\python-2.7.13.msi.
Starting installation...
events.js:182
      throw er; // Unhandled 'error' event
      ^

Error: spawn powershell.exe ENOENT
    at _errnoException (util.js:1024:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:192:19)
    at onErrorNT (internal/child_process.js:374:16)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `node ./lib/index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\p.stepanov\AppData\Roaming\npm-cache\_logs\2017-10-31T07_47_09_032Z-debug.log

Already i:

add the environment variable VCTargetsPath top point at the C++
build tools path
try 2 option from https://github.com/nodejs/node-gyp#on-windows

Can anybody help me?

Источник

Please note that the official Node.js for Windows installer can now automatically install the required tools. That’s likely a much better option than the module listed here (windows-build-tools).

On Windows? Want to compile native Node modules? Install the build tools with this one-liner. Start PowerShell as Administrator and run:

npm install --global windows-build-tools

Or, if you are using Yarn:

yarn global add windows-build-tools

Gif

:bulb: [Windows Vista / 7 only] requires .NET Framework 4.5.1 (Currently not installed automatically by this package)

Visual Studio 2017 vs Visual Studio 2015

This module is capable of installing either the build tools from Visual Studio 2017 or Visual
Studio 2015.

By default, this tool will install the 2017 build tools. To change that, run this script with
the --vs2015 parameter.

Usage

npm [--python-mirror=''] [--proxy=''] [--debug] [--strict-ssl] [--resume] [--sockets=5] [--vcc-build-tools-parameters=''] [--vs2015] [--dry-run-only] install --global windows-build-tools

Optional arguments:

--offline-installers: Path to a folder with already downloaded installers. See
--python-mirror: Use a given mirror to download Python (like --python_mirror=https://npm.taobao.org/mirrors/python/). You can alternatively set a PYTHON_MIRROR environment variable.
--proxy: Use a given proxy. You can alternatively set a PROXY environment variable.
--debug: Be extra verbose in the logger output. Equal to setting the environment variable DEBUG to *.
--strict-ssl: Enables «Strict SSL» mode. Defaults to false.
--resume: By default, windows-build-tools will resume aborted downloads. Set to false to disable.
--sockets: Specifies the number of http sockets to use at once (this controls concurrency). Defaults to infinity.
--vcc-build-tools-parameters: Specifies additional parameters for the Visual C++ Build Tools 2015. See below for more detailed usage instructions.
--silent: The script will not output any information.
--vs2015: Install the Visual Studio 2015 Build Tools instead of the Visual Studio 2017 ones.
--dry-run-only: Don’t actually do anything, just print what the script would have done.
--include-arm64-tools: Include the optional Visual Studio components required to build binaries for ARM64 Windows. Only available with the 2017 and newer build tools and Node.js v12 and up.

Supply parameters to windows-build-tools as a JSON array. Here’s quick example (note the double quotes):

npm --vcc-build-tools-parameters='[""--allWorkloads""]' install --global windows-build-tools

Visual Studio 2015 Parameters

If you run windows-build-tools with --vs2015, these parameters are available:

/AdminFile: Specifies the installation control file.
/CreateAdminFile: Specifies the location to create a control file that can then be used
/CustomInstallPath: Set Custom install location.
/ForceRestart: Always restart the system after installation.
/Full: Install all product features.
/InstallSelectableItems: <item1;item2;…;itemN> Choose which selectable item(s) to be installed.
-selectable item to be installed, just pass in this switch without any value.
/Layout: Create a copy of the media in specified folder.
/NoRefresh: Prevent setup checking for updates from the internet.
/NoRestart: Do not restart during or after installation.
/NoWeb: Prevent setup downloading from the internet.
/Passive: Display progress but do not wait for user input.
/ProductKey: <25-character product key> Set custom product key (no dashes).
/PromptRestart: Prompt the user before restarting the system.
/Repair: Repair the product.
/Uninstall: Uninstall the product.
/Uninstall /Force: Uninstall the product and features shared with other products.

Visual Studio 2017 Parameters

The available parameters are documented here.

Offline Installation

Visual Studio Build Tools: vs_BuildTools.exe or BuildTools_Full.exe
Python: python-3.8.1.amd64.msi or python-3.8.1.msi

Then, run windows-build-tools with the --offline-installers argument:

npm install -g windows-build-tools --offline-installers="C:\Users\John\installers"

Support & Help

Node versions

windows-build-tools 4.0 and up require at least Node v8.
windows-build-tools 3.0 and up require at least Node v6.
windows-build-tools 1.0 and up require at least Node v4.

Where is Python installed?

It’s saved under %USERPROFILE%\.windows-build-tools\python38.

Installing as a Non-Administrator

windows-build-tools works best if installed from an account with administrative rights. However,
thanks to @brucejo75, the following steps can be taken to install to a different user account:

From your non-admin account (e.g. <Me>) run cmd.exe as administrator.
Set the following environment variables in the new command shell:

set APPDATA=C:\Users\<Me>\AppData\Roaming
npm config set prefix C:\Users\<Me>\AppData\Roaming\npm
set USERNAME=<Me>
set USERPROFILE=C:\Users\<Me>

Run npm install -g windows-build-tools

Examples of Modules Supported

In theory, windows-build-tools supports all pure C++ addons for Node.js (and virtually everything
else that requires a native compiler toolchain to be installed on your machine).

License & Credits

Copyright (C) 2018 Felix Rieseberg. Licensed MIT. For more details, please see LICENSE.
This license applies to this package only, not to its dependencies or the 3rd party software that it installs.

Open Source Agenda is not affiliated with «Windows Build Tools» Project. README Source: felixrieseberg/windows-build-tools

Источник

On Windows? Want to compile native Node modules? Install the build tools with this one-liner. Start PowerShell as Administrator and run:

npm install --global windows-build-tools

Or, if you are using Yarn:

yarn global add windows-build-tools

Gif

After installation, npm will automatically execute this module, which downloads and installs Visual
C++ Build Tools, provided free of charge for most users by Microsoft (as part of Visual Studio Community, please consult the license to determine whether or not you’re eligible). These tools are required to compile popular native modules.
If not already installed, it will also install Python 2.7, configuring your machine and npm appropriately.

:bulb: [Windows Vista / 7 only] requires .NET Framework 4.5.1 (Currently not installed automatically by this package)

Visual Studio 2017 vs Visual Studio 2015

This module is capable of installing either the build tools from Visual Studio 2017 or Visual
Studio 2015.

By default, this tool will install the 2017 build tools. To change that, run this script with
the --vs2015 parameter.

Usage

npm [--python-mirror=''] [--proxy=''] [--debug] [--strict-ssl] [--resume] [--sockets=5] [--vcc-build-tools-parameters=''] [--vs2015] [--dry-run-only] install --global windows-build-tools

Optional arguments:

--offline-installers: Path to a folder with already downloaded installers. See
--python-mirror: Use a given mirror to download Python (like --python_mirror=https://npm.taobao.org/mirrors/python/). You can alternatively set a PYTHON_MIRROR environment variable.
--proxy: Use a given proxy. You can alternatively set a PROXY environment variable.
--debug: Be extra verbose in the logger output. Equal to setting the environment variable DEBUG to *.
--strict-ssl: Enables «Strict SSL» mode. Defaults to false.
--resume: By default, windows-build-tools will resume aborted downloads. Set to false to disable.
--sockets: Specifies the number of http sockets to use at once (this controls concurrency). Defaults to infinity.
--vcc-build-tools-parameters: Specifies additional parameters for the Visual C++ Build Tools 2015. See below for more detailed usage instructions.
--silent: The script will not output any information.
--vs2015: Install the Visual Studio 2015 Build Tools instead of the Visual Studio 2017 ones.
--dry-run-only: Don’t actually do anything, just print what the script would have done.
--include-arm64-tools: Include the optional Visual Studio components required to build binaries for ARM64 Windows. Only available with the 2017 and newer build tools and Node.js v12 and up.

Supplying Parameters to the VCC Build Tools

Supply parameters to windows-build-tools as a JSON array. Here’s quick example (note the double quotes):

npm --vcc-build-tools-parameters='[""--allWorkloads""]' install --global windows-build-tools

Visual Studio 2015 Parameters

If you run windows-build-tools with --vs2015, these parameters are available:

/AdminFile: Specifies the installation control file.
/CreateAdminFile: Specifies the location to create a control file that can then be used
/CustomInstallPath: Set Custom install location.
/ForceRestart: Always restart the system after installation.
/Full: Install all product features.
/InstallSelectableItems: <item1;item2;…;itemN> Choose which selectable item(s) to be installed.
-selectable item to be installed, just pass in this switch without any value.
/Layout: Create a copy of the media in specified folder.
/NoRefresh: Prevent setup checking for updates from the internet.
/NoRestart: Do not restart during or after installation.
/NoWeb: Prevent setup downloading from the internet.
/Passive: Display progress but do not wait for user input.
/ProductKey: <25-character product key> Set custom product key (no dashes).
/PromptRestart: Prompt the user before restarting the system.
/Repair: Repair the product.
/Uninstall: Uninstall the product.
/Uninstall /Force: Uninstall the product and features shared with other products.

Visual Studio 2017 Parameters

The available parameters are documented here.

Offline Installation

Visual Studio Build Tools: vs_BuildTools.exe or BuildTools_Full.exe
Python: python-2.7.15.amd64.msi or python-2.7.15.msi

Then, run windows-build-tools with the --offline-installers argument:

npm install -g windows-build-tools --offline-installers="C:\Users\John\installers"

Support & Help

Node versions

windows-build-tools 4.0 and up require at least Node v8.
windows-build-tools 3.0 and up require at least Node v6.
windows-build-tools 1.0 and up require at least Node v4.

Where is Python installed?

It’s saved under %USERPROFILE%\.windows-build-tools\python27.

Installing as a Non-Administrator

windows-build-tools works best if installed from an account with administrative rights. However,
thanks to @brucejo75, the following steps can be taken to install to a different user account:

From your non-admin account (e.g. <Me>) run cmd.exe as administrator.
Set the following environment variables in the new command shell:

set APPDATA=C:\Users\<Me>\AppData\Roaming
npm config set prefix C:\Users\<Me>\AppData\Roaming\npm
set USERNAME=<Me>
set USERPROFILE=C:\Users\<Me>

Run npm install -g windows-build-tools

Examples of Modules Supported

In theory, windows-build-tools supports all pure C++ addons for Node.js (and virtually everything
else that requires a native compiler toolchain to be installed on your machine).

License & Credits

Copyright (C) 2018 Felix Rieseberg. Licensed MIT. For more details, please see LICENSE.
This license applies to this package only, not to its dependencies or the 3rd party software that it installs.

Источник