[windows] How to use npm with node.exe?

I have downloaded Windows Binary (.exe) of nodejs from the main page.

How can I install and use npm (Node package manager)?

I just installed Node.js for the first time and it includes NPM, which can be ran from the Windows cmd. However, make sure that you run it as an administrator. Right click on cmd and choose "run as administrator". This allowed me to call npm commands.

I just installed latest version of node (0.6.12) in Windows 7 using msi (node-v0.6.12.msi).

npm is already shipped with it, no need to include it separately.

I was facing permission issue while running npm (npm install mysql), from the path where my nodejs resided, i.e. C:\Program Files (x86)\nodejs

Then I followed below steps:

1) Added C:\Program Files (x86)\nodejs\npm in environment variables - Path system variable.

2) went back to only C:\ in command prompt and gave the command - npm install mysql - and voila! it worked..

Hope this helps.

The current windows installer from nodejs.org as of v0.6.11 (2012-02-20) will install NPM along with NodeJS.

NOTES:

• At this point, the 64-bit version is your best bet
• The install path for 32-bit node is "Program Files (x86)" in 64-bit windows.
• You may also need to add quotes to the path statement in environment variables, this only seems to be in some cases that I've seen.
• In Windows, the global install path is actually in your user's profile directory
  • %USERPROFILE%\AppData\Roaming\npm
  • %USERPROFILE%\AppData\Roaming\npm-cache
  • WARNING: If you're doing timed events or other automation as a different user, make sure you run npm install as that user. Some modules/utilities should be installed globally.
  • INSTALLER BUGS: You may have to create these directories or add the ...\npm directory to your users path yourself.

To change the "global" location for all users to a more appropriate shared global location %ALLUSERSPROFILE%\(npm|npm-cache) (do this as an administrator):

• create an [NODE_INSTALL_PATH]\etc\ directory
  • this is needed before you try npm config --global ... actions
• create the global (admin) location(s) for npm modules
  • C:\ProgramData\npm-cache - npm modules will go here
  • C:\ProgramData\npm - binary scripts for globally installed modules will go here
  • C:\ProgramData\npm\node_modules - globally installed modules will go here
  • set the permissions appropriately
    • administrators: modify
    • authenticated users: read/execute
• Set global configuration settings (Administrator Command Prompt)
  • npm config --global set prefix "C:\ProgramData\npm"
  • npm config --global set cache "C:\ProgramData\npm-cache"
• Add C:\ProgramData\npm to your System's Path environment variable

If you want to change your user's "global" location to %LOCALAPPDATA%\(npm|npm-cache) path instead:

• Create the necessary directories
  • C:\Users\YOURNAME\AppData\Local\npm-cache - npm modules will go here
  • C:\Users\YOURNAME\AppData\Local\npm - binary scripts for installed modules will go here
  • C:\Users\YOURNAME\AppData\Local\npm\node_modules - globally installed modules will go here
• Configure npm
  • npm config set prefix "C:\Users\YOURNAME\AppData\Local\npm"
  • npm config set cache "C:\Users\YOURNAME\AppData\Local\npm-cache"
• Add the new npm path to your environment's PATH.
  • setx PATH "%PATH%;C:\Users\YOURNAME\AppData\Local\npm"

For beginners, some of the npm modules I've made the most use of are as follows.

• axios - for more complex http posts/gets
• isomorphic-fetch - for http(s) post/get requests
• node-mailer - smtp client
• mssql - interface and driver library for querying MS SQL Server (wraps tedious)

More advanced JS options...

• async/await - async functions, supported via babel

For testing, I reach for the following tools...

• mocha - testing framework
• chai - assertion library, I like chai.expect
• sinon - spies and stubs and shims
• sinon-chai - extend chai with sinon's assertion tools
• babel-istanbul - coverage reports
• jest - parallel testing, assertions, mocking, coverage reports in one tool
• babel-plugin-rewire - slightly easier for some mocking conditions vs. jest

Web tooling.

• webpack - module bundler, package node-style modules for browser usage
• babel - convert modern JS (ES2015+) syntax for your deployment environment.

If you build it...

• shelljs - shell utilities for node scripts,. I used to use gulp/grunt, but these days will have a scripts directory that's referenced in package.json scripts via npm. You can use gulp tools inside plain scripts.

When Node.js is not installed using the msi installer, npm needs to be setup manually.

setting up npm

First, let's say we have the node.exe file located in the folder c:\nodejs. Now to setup npm-

1. Download the latest npm release from GitHub (https://github.com/npm/npm/releases)
2. Create folders c:\nodejs\node_modules and c:\nodejs\node_modules\npm
3. Unzip the downloaded zip file in c:\nodejs\node_modules\npm folder
4. Copy npm and npm.cmd files from c:\nodejs\node_modules\npm\bin to c:\nodejs folder

In order to test npm, open cmd.exe change working directory to c:\nodejs and type npm --version. You will see the version of npm if it is setup correctly.

Once setup is done, it can be used to install/uninstall packages locally or globally. For more information on using npm visit https://docs.npmjs.com/.

As the final step you can add node's folder path c:\nodejs to the path environment variable so that you don't have to specify full path when running node.exe and npm at command prompt.

I am running node.js on Windows with npm. The trick is simply use cygwin. I followed the howto under https://github.com/joyent/node/wiki/Building-node.js-on-Cygwin-(Windows) . But make sure that you use version 0.4.11 of nodejs or npm will fail!

Here is a guide by @CTS_AE on how to use NPM with standalone node.exe: https://stackoverflow.com/a/31148216/228508

1. Download the node.exe stand-alone from nodejs.org
2. Grab an NPM release zip off of github https://github.com/npm/npm/releases
3. Create a folder named: node_modules in the same folder as node.exe
4. Extract the NPM zip into the node_modules folder
5. Rename the extracted npm folder to npm and remove any versioning ie: npm-3.3.4 –> npm.
6. Copy npm.cmd out of the /npm/bin/ folder into the root folder with node.exe

I've just installed 64 bit Node.js v0.12.0 for Windows 8.1 from here. It's about 8MB and since it's an MSI you just double click to launch. It will automatically set up your environment paths etc.

Then to get the command line it's just [Win-Key]+[S] for search and then enter "node.js" as your search phrase.

Choose the Node.js Command Prompt entry NOT the Node.js entry.

Both will given you a command prompt but only the former will actually work. npm is built into that download so then just npm -whatever at prompt.

Use a Windows Package manager like chocolatey. First install chocolatey as indicated on it's homepage. That should be a breeze

Then, to install Node JS (Install), run the following command from the command line or from PowerShell:

C:> cinst nodejs.install

Search all .npmrc file in your system.

Please verify that the path you have given is correct. If not please remove the incorrect path.