-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 run" appears not to work #541
Comments
Do you have “ignore-scripts” set in your global npm config? |
I just checked the global config folder: In my case, no such folder existed. I then checked the per-user config file: To my surprise, the file contained this (as you suspected): I set it to this: Then retried:
Question: Any idea how this setting gets made? I'm pretty sure I didn't do it (as far as I know). |
You probably followed some paranoid tutorial that suggested disabling that setting systemwide with |
I'm having the same issue. |
@jeffminsungkim thats a different issue, i think. |
@ljharb - thanks for resolving my issue! |
@ljharb thanks for the solution |
installing npm install --save-dev nodemon and running npm start did the magic for me |
What / Why
"npm run" appears not to work - generates no output.
When
On a command line (Windows "CMD.EXE")
Where
Windows Home (Version 1909)
node -v
: v12.13.1npm -v
: 6.12.1How
Current Behavior
npm run
generates no outputSteps to Reproduce
On a command line (Windows "CMD.EXE"):
md npm-run-issue
cd npm-run-issue
npm init
Edit contents of package.json:
npm run echo
No output (at all) is generated.
Expected Behavior
Output should be similar to that from "yarn run":
yarn run v1.9.4
$ echo 'run' works!
'run' works!
Done in 0.12s.
References
The issue can be reproduced locally with this GitHub repository:
https://github.com/snerks/npm-run-issue
The text was updated successfully, but these errors were encountered: