Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support running jest command from a path that is not the project's root
See original GitHub issueThis https://github.com/orta/vscode-jest/pull/25 wasn’t quite right in the end, I need to run npm run jest -- --watch from the root of the jest repo in order to ensure the build transformations work right. So ideally, I’d be able to say “if I open at this folder, use this as cwd for jest”.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Jest CLI Options
You can run jest --help to view all available options. ... If no rootDir is set in the config, the directory containing the...
Read more >Run Jest tests only for current folder - Stack Overflow
For e.g. if I go to c:/dev/app in terminal and type some-jest-command , it should only run files with .test.js present in the...
Read more >jest: command not found error [Solved] | bobbyhadz
Use `npx` to solve the error jest: command not found, e.g. `npx jest` or install the package globally by running `npm install -g...
Read more >Run/Debug Configuration: Jest | IntelliJ IDEA Documentation
In this dialog, create configurations for running Jest tests. ... By default, the Working directory field shows the project root folder.
Read more >Supported technologies: Jest, Snapshot Testing - Wallaby.js
To start Wallaby in VS Code you may run Select Configuration command and then select Automatic Configuration <project directory> option once.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Exception raised: Process failed: spawn npm ENOENTcan you try setting your
jest.pathToJestfor this project to benpm test --?