Timeline for 'command not found: jest'
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 24, 2021 at 17:45 | history | edited | CaptEmulation | CC BY-SA 4.0 |
Updated with newer yarn behavior
|
| Mar 24, 2021 at 15:20 | comment | added | Timo |
do I need jest-cli to run jest in cmd? npm t should be fine, so why bother with jest-cli and add this package?
|
|
| Jun 10, 2020 at 11:49 | comment | added | Marc |
Why does npm test work on windows but not on linux? In neither system is jest installed globally but in windows it runs fine and in linux it says " jest: command not found"
|
|
| Mar 4, 2020 at 15:06 | comment | added | James Webb | I just ran into this issue where I had been using jest on the CLI fine until suddenly jest was an 'unknown command'. Turns out I had used NVM to switch to a older version of node (10.13.0) and I think this switches the NPM version as well. Switching back to 10.17.0 fixed this issue for me. So I assume NPM adds ./node_modules/.bin to the path in later versions. | |
| Feb 20, 2020 at 11:30 | comment | added | SBUK-Tech | Documentation on above answer: jestjs.io/docs/en/cli.html#using-with-npm-scripts | |
| Feb 20, 2020 at 11:29 | comment | added | SBUK-Tech |
If you have modified your package test script and want quick direct access to jest via your node modules you could also add a system link. ln -s ./node_modules/.bin/jest jest and then use it with ./jest
|
|
| Feb 3, 2019 at 18:14 | comment | added | CaptEmulation |
test and start are special fields in scripts' that can be executed without npm run. npm test` is the same command as npm run test
|
|
| Feb 1, 2019 at 9:20 | comment | added | 31415926 | what exactly npm test -- do in this case? where this -- documented? | |
| May 2, 2018 at 16:09 | vote | accept | Aessandro | ||
| May 2, 2018 at 15:45 | history | answered | CaptEmulation | CC BY-SA 4.0 |