Menu
I ran npm install
on a project and it gives a number of errors and warnings that I want to catch, but the output is too long and being cut off so I can't view the full list in the terminal.
I tried redirect it to a file but the output is still being written to the terminal and I still get an output file which only list the dependency trees.
I also tried to pipe it to less in linux but it still run through many screens until stopped for continue.
I checked npm doc and it doesn't seem to have log functionality, what I want is to be able to log the exact output in a file, how can I do it?
442
The default location of the logs directory is a directory named _logs inside the npm cache. This can be changed with the logs-dir config option.
To find your . npm directory, use npm config get cache . If you use a CI environment, your logs are likely located elsewhere. For example, in Travis CI, you can find them in the /home/travis/build directory.
Example usage: npm install ionic --loglevel verbose . Running the npm commands like this, shows the logs in realtime and saves the logs to the directory its running within. For permanent solution, just edit the global npm configuration. To do this, run npm config edit command and add loglevel=verbose .
To see if NPM is installed, type npm -v in Terminal. This should print NPM's version number so you'll see something like this 1.4.
If you need to generate a npm-debug.log file, you can run one of these commands. You can find the npm-debug.log file in your .npm directory. To find your .npm directory, use npm config get cache. If you use a CI environment, your logs are likely located elsewhere.
All logs are written to a debug log, with the path to that file printed if the execution of a command fails. The log levels listed above have various corresponding aliases, including: The npm CLI began hiding the output of lifecycle scripts for npm install as of v7.
The npm CLI began hiding the output of lifecycle scripts for npm install as of v7. Notably, this means you will not see logs/output from packages that may be using "install scripts" to display information back to you or from your own project's scripts defined in package.json.
When a package fails to install or publish, the npm CLI will generate an npm-debug.log file. This log file can help you figure out what went wrong. If you need to generate a npm-debug.log file, you can run one of these commands.
npm install 2>&1 | tee log.txt
The 2>&1 routes stderr to stdout, so everything will output in a single stream.
115
You may only be interested in the warnings and errors, if so try this:
The npm arg is
--silent. Ornpm config set loglevel warnif you want to only print warnings and errors. Or you can pipe it to/dev/null.
so you have 2 options:
npm i --silentnpm config set loglevel warn then npm i
References:
npm install should be quiet
Add option to hide summary output from npm install
22
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
