-
-
Notifications
You must be signed in to change notification settings - Fork 242
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
ignoring of config variables overwritten via command line #13
Comments
So I did a lot and was doing it all over the place all the times, and I was very lax about commits. So I’m sorry. I’ve added documentation for each of the scripts that we have. All of them do the thing that we expect them to (as far as I know), and we now have a nice npm run help thing too.
Thank you for reporting and providing the test case! |
OK, I had not noticed this feature. Please wait for a few days to release... (I don't have enough time in weekdays) |
Hi So for now it does not work at all :(. i got: ERROR: test:t: None-Zero Exit(7); in npm-debug.log one can see more details: ⌘ cat npm-debug.log.c6eddc672a318240c004b7a835d29ae0 |
I'm sorry. |
I believe this feature is working now. |
Hey |
It seems i have no permission to reopen that issue, but definitely it shall be re opened |
I think that's expected behavior because diff --git a/package.json b/package.json
index 05d2bd0..bf58b4b 100644
--- a/package.json
+++ b/package.json
@@ -8,8 +8,8 @@
"main": "index.js",
"scripts": {
"test": "npm-run-all test:*",
- "test-2": "npm-run-all test:t",
- "test:t": "mocha --reporter ${npm_package_config_reporter}"
+ "test-2": "npm run test:t",
+ "test:t": "mocha --reporter %npm_package_config_reporter%"
},
"keywords": [],
"author": "",
|
Hmm, but the purpose is different between |
Now, |
Hi
I bumped into a problem that npm-run-all does not propagate overwritten configuration parameters (via command line) when running tasks.
To be more precise:
when i run a package script from command line and overwrite configuration parameters (via --<project.name>:<configuraton_param_name>=<configuration_param_value> ) than everything is fine, ie. my script command would be run against overwritten parameters.
But if my package script command executes npm-run-all than any of "run-all" tasks are not handed overwritten parameters.
I did create a small test case https://github.com/jmilkiewicz/npm-run-all-bug
which uncovers that issue. The case is based on specifying custom matcher for mocha via configuration parameters.
The text was updated successfully, but these errors were encountered: