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.
Jest // markers at non-test files.
See original GitHub issueHi since the last update of vscode-jest, I randomly find empty jest markers // at non test files.
Im on vscode-jest 2.2.0 / jest 20.0.3 / create-react-app canary …
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Jest CLI Options
The jest command line runner has a number of useful options. You can run jest --help to view all available options. Many of...
Read more >`require-hook` rule checks non-test files · Issue #934 · jest- ...
Hello, first of all: thanks for your work! I'm currently facing an issue upgrading to v25.0.1 due to the require-hook rule. This rule...
Read more >How do I test a single file using Jest? - node.js
To access jest directly on the command line, install it via npm i -g jest-cli or yarn global add jest-cli . Then simply...
Read more >Jest testing without the noise
Running 1 test file at a time. You know that feeling when you you are writing Jest tests and for you to check...
Read more >cosplay craft
The cosplayer that won the BlerdCon 2021 Cosplay Contest is a White ... this is adjusted for FOAM cosplay and the files aren't...
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
Do you have a sample repository we can look at to try to reproduce?
Not quite the same cause, but the symptom is the same. If an error stack trace has an incorrect line number when it’s transpiled and mapped, you can get some weird results. It happens in our repo. 😞
If anyone’s seeing this behavior again, it’d be helpful to include the contents of the Jest Output channel so we can try to determine where the stack trace parsing may be going wrong.