Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] NPM passes the --ignore-scripts option to all dependencies. #6519

Closed
2 tasks done
frbuceta opened this issue Jun 2, 2023 · 2 comments
Closed
2 tasks done

[BUG] NPM passes the --ignore-scripts option to all dependencies. #6519

frbuceta opened this issue Jun 2, 2023 · 2 comments
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 9.x work is associated with a specific npm 9 release

Comments

@frbuceta
Copy link

frbuceta commented Jun 2, 2023

Is there an existing issue for this?

  • I have searched the existing issues

This issue exists in the latest npm version

  • I am using the latest npm

Current Behavior

I install a package of my own that contains sqlite3 which itself contains an install script. When I run npm ci --ignore-scripts in my project, the sqlite3 does not execute the install script.

Expected Behavior

Running npm ci --ignore-scripts should only ignore the scripts in my packages.

Steps To Reproduce

loopbackio/loopback-next#9562 See tests

Environment

  • npm: 9.6.7
  • Node.js: 18.15.0
  • OS Name: GitHub Actions (ubuntu, macos, windows)
  • System Model Name: CI
  • npm config:
; "user" config from /home/fran/.npmrc

//registry.npmjs.org/:_authToken = (protected) 

; "project" config from /home/fran/Projects/loopback-next/.npmrc

package-lock = true 
scripts-prepend-node-path = true 

; node bin location = /usr/bin/node
; node version = v18.15.0
; npm local prefix = /home/fran/Projects/loopback-next
; npm version = 9.6.7
; cwd = /home/fran/Projects/loopback-next
; HOME = /home/fran
; Run `npm config ls -l` to show all defaults.
@frbuceta frbuceta added Bug thing that needs fixing Needs Triage needs review for next steps Release 9.x work is associated with a specific npm 9 release labels Jun 2, 2023
@ljharb
Copy link
Contributor

ljharb commented Jun 2, 2023

The primary purpose of the flag is to ignore scripts in installed deps imo.

@wraithgar
Copy link
Member

This is not a bug this is by design and as stated is the original purpose behind the flag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 9.x work is associated with a specific npm 9 release
Projects
None yet
Development

No branches or pull requests

3 participants