Allow cli to be executed against arbitrary package.json scripts?

Let’s say I have package.json scripts declaration like this:

"scripts": {
  "stats": "webpack --profile --json > stats.json",
  "start": "webpack-dev-server",
  "deploy": "gh-pages -d build",
  "build": "webpack",
  "test": "karma start",
  "test:tdd": "karma start --auto-watch --no-single-run",
  "test:lint": "eslint . --ext .js --ext .jsx --ignore-path .gitignore --ignore-pattern dist --cache"
},

I would like to run webpack-validator cli against all of these (separate script) without having to spell each script explicitly.

My current tooling figures out which webpack configuration to run based on process.env.npm_lifecycle_event. I would need some neat way to run the validator while setting that against each script name.

How would you solve this? I could probably handle it outside of webpack-validator but some kind of integration might be cool as well. Then you would perhaps point the validator to package.json and it would just work.

If we can agree on a specification, I could implement it.

[bebraw]

--all-scripts would be cool, yeah.

The implementation takes a couple of further tweaks (need to do path.join against process.cwd() etc.) but I don’t mind doing a PR.

[jonathanglasmeyer]

Ok, now I understand it much better. Well, it’ll probably be really handy for 80 percent of people’s setups. As long as we have an explicit description what it can and can’t do in the README, I think we can put it on the cli, maybe with --all-scripts, --from-scripts or --scripts?