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.
vscode-jest does not start when the workspace folder name (multi-root) contains blanks
See original GitHub issueEnvironment
node -v: 10.5npm -v: 6.1- VSCode: 1.24.1
- Operating system: Windows 10 1709
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:11
Top Results From Across the Web
vscode jest extension doesn't work properly - Stack Overflow
Explanation: When using Workspaces you can have multiple projects in one folder. Each will be count as a root project. The Workspace allows...
Read more >Debug Node.js Apps using Visual Studio Code
The Visual Studio Code editor includes Node.js debugging support. Set breakpoints, step-in, inspect variables and more.
Read more >VScode-jest: The Optimal Flow for Jest Based Testing in VS ...
VScode -jest: The optimal flow for Jest based testing in VS Code. Jest - Visual Studio Marketplace & click "Install". Alternatively open Visual...
Read more >Source - GitHub
@connectdotz (#737) * support official vscode Test Explorer and API in v1.59 ... location bug such as for jest.todo tests (#657) - @connectdotz...
Read more >Visual Studio Code tips for monorepo development with Multi ...
There is not much to do to make Visual Studio Code work in monorepos: by default, ... Multi-root workspaces can contain different folders, ......
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
Fixed by using: “jest.pathToJest”: “npm run test --” instead of “jest.pathToJest”: “npm run test”
It also happens with special characters for me.