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.
Avoid magic (babel unclear requirement)
See original GitHub issue🐛 Bug Report
Currently jest (23.6.0) fails if @babel/core or babel-core or babel-jest are not installed. This just happens if any other dependency in my app installed any @babel/xxxx or babel-xxxx package in node_modules/.
My app uses ES6 (const, class, etc) but it does not use import/export so I see no reason for jest to require babel at all (I’m running it in Node >= 8).
Magic is not good. My app (dev) dependencies should not depend on whether other deps install babel stuff in my node_modules. I shouldn’t have to install babel stuff within my devDependencies to just run jest.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We use babel internally for things like hoisting jest.mock to the top of files for you
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.