Passing CLI args to pre-command in package.json

Question

Let's say I have in my package.json:

{
  "scripts": {
    "prebuild": "some-command",
    "build": "some-other-command"
  }
}

If I now run npm run build -- --some-args, the prebuild command some-command does not get the --some-args passed to it. How can I pass this to all the pre/post scripts as well?

@jonrsharpe looks like this did happen at one point? https://github.com/npm/npm/issues/6343 — Kousha, Apr 29 '20 at 20:25
The question asks for either doing a `pre` or chaining commands using `&&`. The answer only speaks of the former. — Kousha, Apr 29 '20 at 20:29
Well you've illustrated the behaviour for yourself and found where it was taken out, it's hard to see what's still confusing. — jonrsharpe, Apr 29 '20 at 20:35

score 0 · Answer 1 · answered Apr 29 '20 at 20:56

You might be able to do it using environment variable:

"scripts": {                                                                  
    "prebuild": "echo $FLAG \"prebuild\"",                                
    "build": "echo \"testing\""                                                     
}

If you run npm run build:


> test@1.0.0 prebuild /test
> echo $FLAG "prebuild"

prebuild

> test@1.0.0 build /test
> echo "testing"

testing

And if you run FLAG=-n npm run build:

> test@1.0.0 prebuild /test
> echo $FLAG "prebuild"

prebuild
> test@1.0.0 build /test
> echo "testing"

testing

However I'm not sure if it will work with multiple flags

You don't need to actually do the `echo $FLAG` environment variables are passed to pre/post scripts — Kousha, Apr 29 '20 at 21:11

Passing CLI args to pre-command in package.json

1 Answers1