dependabot/npm_and_yarn/main/proc-log-7.0.0
@reggi/path-to-regexp
dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2
dependabot/npm_and_yarn/main/eslint-10.4.0
dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0
dependabot/npm_and_yarn/main/proc-log-7.0.0
dependabot/npm_and_yarn/npm_and_yarn-826852524d
dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2
deprecate-totp-2fa
dhei/classic-tokens
gat-bypass-2fa-docs
jpg619/fix-accessibility-content-flow
jpg619/version-bump-tar-2
kartykp/gat-bypass-2fa-docs
kartykp/upgrade-path-to-regex
main
maitxn/version-bump-tar
patch-1
reggi/cache-based-on-version
reggi/dev-engines
reggi/fix-transform-prettier
reggi/overrides
update-search-sensitivity
| 1 | --- |
| 2 | title: Generating and locating npm-debug.log files |
| 3 | redirect_from: |
| 4 | - /generating-and-locating-npm-debug-log-files |
| 5 | --- |
| 6 | |
| 7 | 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. |
| 8 | |
| 9 | If you need to generate a `npm-debug.log` file, you can run one of these commands. |
| 10 | |
| 11 | For installing packages: |
| 12 | |
| 13 | ``` |
| 14 | npm install --timing |
| 15 | ``` |
| 16 | |
| 17 | For publishing packages: |
| 18 | |
| 19 | ``` |
| 20 | npm publish --timing |
| 21 | ``` |
| 22 | |
| 23 | You can find the `npm-debug.log` file in your `.npm` directory. To find your `.npm` directory, use `npm config get cache`. |
| 24 | |
| 25 | 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. |