You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After following the installation instructions from the README, npm run pretest fails;
$ npm list no-skipped-tests
my-project@1.0.125 ~/projects/my-project
└── no-skipped-tests@1.0.0
$ npm run pretest
> my-project@1.0.125 pretest ~/projects/my-project
> no-skipped-tests
sh: no-skipped-tests: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! my-project@1.0.125 pretest: `no-skipped-tests`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the my-project@1.0.125 pretest script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! ~/.npm/_logs/2019-05-06T02_17_06_493Z-debug.log
The text was updated successfully, but these errors were encountered:
BevanR
changed the title
Instalation instructions out of date?
🐞 Instalation instructions out of date?
May 6, 2019
dominique-mueller
changed the title
🐞 Instalation instructions out of date?
🐞 Installation instructions out of date?
Apr 17, 2020
dominique-mueller
added
needs repro
Indicates that this issue needs a reproduction before further steps can be taken
support
Indicates a request for help / clarification
type: documentation
Indicates wrong, unclear, missing or hard to understand documentation
and removed
needs repro
Indicates that this issue needs a reproduction before further steps can be taken
support
Indicates a request for help / clarification
labels
Apr 17, 2020
Yes, you're right, the README has a copy-paste issue. You can of course run npm run pretest but only if that script is set up. Running the tool itself without that script can be done using npm run no-skipped-tests.
After following the installation instructions from the README,
npm run pretest
fails;The text was updated successfully, but these errors were encountered: