If anyone finds a better way, sound off in the comments below. $errors = powershell.exe -Command "cd `"c:\path\to\dest" `n npm install"
#NPM INSTALL OPTIONS D HOW TO#
The output is sent to the host shell, and the errors are returned as a result variable. 01 - What is npm 02 - How to find & select packages 03 - How to set up a new npm account & install npm 04 - How to install local packages 05 - Working with package.json 06 - How to update local packages 07 - How to uninstall local packages 08 - How to install global packages 09 - How to update global packages 10 - How to uninstall global. The easiest path to that is calling powershell.exe -Command. The option I’ve settled upon is calling an external process and getting all the output for the external process in the current window. bin folder as expected, however, the node_modules folder you want will be c:\path\to\dest2\node_modules\\node_modules\.bin, so you would need run this command setting the prefix to a tmp folder then copy the folder to the correct location, at the cost of extra IO. npm install -cwd "c:\path\to\dest" -prefix "c:\path\to\dest2" If you change the target directory for the -prefix flag, it creates a nested hierarchy. So it acts as if you’re doing an install to the global NPM folder. The dependencies install, but the bin links, like bash scripts and cmd files, are stored in the c:\path\to\dest instead of c:\path\to\dest\node_modules\.bin which one would expect for a local install. By default, npm install will install all modules listed as dependencies in.
In global mode (ie, with -g or -global appended to the command), it installs the current package context (ie, the current working directory) as a global package. I’ve seen posts talking using -prefix to accomplish this, however, if I do the following on Windows: npm install -cwd "c:\path\to\dest" -prefix "c:\path\to\dest" npm install (in package directory, no arguments): Install the dependencies in the local nodemodules folder. It just feels hacky to change the directory away from root working directory for a build. My primary objective for running NPM from a different folder is the use case of using build scripts. I find that trying to run NPM install for all dependencies in a different folder than where the package.json resides,… a bit troublesome.
0 kommentar(er)
