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.
What's the verdict on `mjs` support?
See original GitHub issueIs this a bug report?
No, It’s a question on the release conventions of the project. I was wondering how fixes for the current release are ported to the next branch?
I was depending on this bug fix https://github.com/facebook/create-react-app/pull/4085/files, from 1.1.2 but then needed some updated dependencies, so started using react-scripts@next but found that that fix is not present.
I’d expect all of master/current release to be merged into next is that not the case? or is it a manual process?
Thanks in advance! 👍
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:11 (9 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’re dropping
mjssupport in 2.0 until Jest supports it, please follow https://github.com/facebook/jest/issues/4842.I see in the latest webpack.config.dev.js for react-scripts that we have .mjs before .js in the extensions list