This repository has been archived by the owner. It is now read-only.

Cannot run script before install a new dependency into my project #18857

Open
sarkiroka opened this Issue Oct 16, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@sarkiroka

sarkiroka commented Oct 16, 2017

I'm opening this issue because:

  • npm is crashing.
  • npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?

I want to save time of my developers. We use nsp to check security problems for node modules, and we want to check it before it installed on local envrionment. For example I want to stop the installation procedure, and show error message to developer who want install the older version of minimatch because it vulnerable.

How can the CLI team reproduce the problem?

We try to use install and preinstall scripts, but it ineffective when we use a new module
npm i minimatch@1 --save

The expected usage is a new script - for example preadddependency where we can check the new module security problems with nsp, and it can blocking the installation procedure (package.json doesn't change)

@KenanY KenanY added the lifecycle label Oct 16, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.