Skip to content
This repository has been archived by the owner on Sep 11, 2021. It is now read-only.

Commit

Permalink
📝 Remove production advisory
Browse files Browse the repository at this point in the history
  • Loading branch information
felixrieseberg committed Sep 10, 2018
1 parent d11a4dc commit 4420dc8
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
On Windows? Want to compile [native Node modules](#examples-of-modules-supported)? Install the build tools with this one-liner. Start PowerShell as Administrator and run:

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

Or, if you are using Yarn:
Expand Down Expand Up @@ -105,7 +105,7 @@ have their original names:
Then, run `windows-build-tools` with the `--offline-installers` argument:

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

## Support & Help
Expand Down Expand Up @@ -141,7 +141,7 @@ of user profiles on your machine. For `<me>`, substitute the name of the account
install `windows-build-tools` for. For more information, see the `npm config set prefix`
description [here](https://docs.npmjs.com/getting-started/fixing-npm-permissions).

3. Run `npm install -g --production windows-build-tools`
3. 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
Expand Down

0 comments on commit 4420dc8

Please sign in to comment.