Skip to content

Commit

Permalink
Docs: mention npm's foreground-scripts option to aid debugging
Browse files Browse the repository at this point in the history
  • Loading branch information
lovell committed Apr 18, 2022
1 parent 985e881 commit 36e5596
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions .github/ISSUE_TEMPLATE/installation.md
Expand Up @@ -32,11 +32,11 @@ If you are using npm v7 or later, does the user running `npm install` own the di

If you are using the `ignore-scripts` feature of `npm`, have you tried with the `npm install --ignore-scripts=false` flag?

### What is the complete output of running `npm install --verbose sharp`?
### What is the complete output of running `npm install --verbose --foreground-scripts sharp` in an empty directory?

<details>

<!-- Please provide output of `npm install --verbose sharp` here. -->
<!-- Please provide output of `npm install --verbose --foreground-scripts sharp` in an empty directory here. -->

</details>

Expand Down
2 changes: 1 addition & 1 deletion docs/install.md
Expand Up @@ -57,7 +57,7 @@ When using npm v7 or later, the user running `npm install` must own the director

The `npm install --ignore-scripts=false` flag must be used when `npm` has been configured to ignore installation scripts.

Check the output of running `npm install --verbose sharp` for useful error messages.
Check the output of running `npm install --verbose --foreground-scripts sharp` for useful error messages.

## Apple M1

Expand Down

0 comments on commit 36e5596

Please sign in to comment.