-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What's the verdict on mjs
support?
#4317
Comments
I believe it was cherry picked to next but we haven’t cut a new next version yet. Plan to in a few days. |
Okay, thanks for the clarification @gaearon will wait for the next |
Oh it looks like it hasn't been cherry-picked into |
This was intentionally not cherry-picked because it's a sub-optimal bugfix. |
mjs
support?
@Timer oh thanks for pointing that out, read the full thread now and agree it's suboptimal. Shall I close the PR and keep the issue open so we can track the mjs plan? |
You can leave the PR open; if we don't figure out proper support we'll probably roll with it. Would you like to help with ensuring proper support? The Jest feature request would be a great start. |
What exactly do we need for proper support? Is it just Jest and webpack handling |
Jest and then we need to make sure that webpack resolves starting with |
3 months later -- where are with with this? |
I see in the latest webpack.config.dev.js for react-scripts that we have .mjs before .js in the extensions list |
We're dropping |
Is 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! 👍
The text was updated successfully, but these errors were encountered: