mirror of
https://github.com/nodejs/node.git
synced 2025-05-09 09:08:46 +00:00
2d84620f86
PR-URL: https://github.com/nodejs/node/pull/42550 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Mestery <mestery@protonmail.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com> Reviewed-By: Tierney Cyren <hello@bnb.im> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com>
88 lines
3.1 KiB
Markdown
88 lines
3.1 KiB
Markdown
---
|
|
title: Logging
|
|
section: 7
|
|
description: Why, What & How We Log
|
|
---
|
|
|
|
### Description
|
|
|
|
The `npm` CLI has various mechanisms for showing different levels of information back to end-users for certain commands, configurations & environments.
|
|
|
|
### Setting Log File Location
|
|
|
|
All logs are written to a debug log, with the path to that file printed if the execution of a command fails.
|
|
|
|
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.
|
|
|
|
Log files will be removed from the `logs-dir` when the number of log files exceeds `logs-max`, with the oldest logs being deleted first.
|
|
|
|
To turn off logs completely set `--logs-max=0`.
|
|
|
|
### Setting Log Levels
|
|
|
|
#### `loglevel`
|
|
|
|
`loglevel` is a global argument/config that can be set to determine the type of information to be displayed.
|
|
|
|
The default value of `loglevel` is `"notice"` but there are several levels/types of logs available, including:
|
|
|
|
- `"silent"`
|
|
- `"error"`
|
|
- `"warn"`
|
|
- `"notice"`
|
|
- `"http"`
|
|
- `"timing"`
|
|
- `"info"`
|
|
- `"verbose"`
|
|
- `"silly"`
|
|
|
|
All logs pertaining to a level proceeding the current setting will be shown.
|
|
|
|
##### Aliases
|
|
|
|
The log levels listed above have various corresponding aliases, including:
|
|
|
|
- `-d`: `--loglevel info`
|
|
- `--dd`: `--loglevel verbose`
|
|
- `--verbose`: `--loglevel verbose`
|
|
- `--ddd`: `--loglevel silly`
|
|
- `-q`: `--loglevel warn`
|
|
- `--quiet`: `--loglevel warn`
|
|
- `-s`: `--loglevel silent`
|
|
- `--silent`: `--loglevel silent`
|
|
|
|
#### `foreground-scripts`
|
|
|
|
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`. If you'd like to change this behavior & log this output you can set `foreground-scripts` to `true`.
|
|
|
|
### Timing Information
|
|
|
|
The `--timing` config can be set which does two things:
|
|
|
|
1. Always shows the full path to the debug log regardless of command exit status
|
|
1. Write timing information to a timing file in the cache or `logs-dir`
|
|
|
|
This file is a newline delimited list of JSON objects that can be inspected to see timing data for each task in a `npm` CLI run.
|
|
|
|
### Registry Response Headers
|
|
|
|
#### `npm-notice`
|
|
|
|
The `npm` CLI reads from & logs any `npm-notice` headers that are returned from the configured registry. This mechanism can be used by third-party registries to provide useful information when network-dependent requests occur.
|
|
|
|
This header is not cached, and will not be logged if the request is served from the cache.
|
|
|
|
### Logs and Sensitive Information
|
|
|
|
The `npm` CLI makes a best effort to redact the following from terminal output and log files:
|
|
|
|
- Passwords inside basic auth URLs
|
|
- npm tokens
|
|
|
|
However, this behavior should not be relied on to keep all possible sensitive information redacted. If you are concerned about secrets in your log file or terminal output, you can use `--loglevel=silent` and `--logs-max=0` to ensure no logs are written to your terminal or filesystem.
|
|
|
|
### See also
|
|
|
|
* [config](/using-npm/config)
|