Extension thinks I'm using old jest
See original GitHub issueI get this message on vscode startup: “This extension relies on Jest 20+ features, it will continue to work, but some features may not work correctly.”
But I am using jest 20, installed into my node_modules:
$ node_modules/.bin/jest -v
v20.0.4
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:15 (7 by maintainers)
Top Results From Across the Web
Troubleshooting - Jest
Use this guide to resolve issues with Jest. Tests are Failing and You Don't Know Why. Try using the debugging support built into...
Read more >jest unexpected token when importing css - Stack Overflow
The problem is that Jest is hitting these CSS imports and trying to parse them as if they were JavaScript. The "Unexpected token...
Read more >React Testing Library Tutorial - Robin Wieruch
Learn how to use React Testing Library in this tutorial. You will learn how to test your React components step by step with...
Read more >Integration Testing Browser Extensions with Jest - Medium
Today I am happy to report that I have found a way to perform integration testing on extensions and want to share it...
Read more >React Components Testing with React Testing Library and Jest
It is super easy to use, provides an array of assertion methods (extended from Jest), user-events simulation and etc. create-react-app uses Jest as...
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 FreeTop 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
Top GitHub Comments
@seanpoulter Found where it was checking the path to Jest and added a line (and subsequent test) to check for jest-cli as well. Opened a PR for this. #243
I actually uninstalled the extension when it first started happening because I couldn’t make it behave. I re-installed it when I saw your comment so I’d guess that fixed it 😃
Yeah, I’ve noticed that - I’ve taken to using
npx jest --watch
instead