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
_index.mjs
may not be resolved for some reason in legacy projects
#12902
Comments
Hey @fengxinming! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly. If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite." |
_index.mjs
of @babel/runtime@7.13.x may not be resolved for some reason in legacy projects_index.mjs
may not be resolved for some reason in legacy projects
Hi @fengxinming! This issue is missing some important information we'll need to be able to reproduce this issue. Please understand that we receive a high volume of issues, and there are only a limited number of volunteers that help maintain this project. The easier it is for us to decipher an issue with the info provided, the more likely it is that we'll be able to help. Please make sure you have the following information documented in this ticket:
Please provide either a link to the problem via the |
@afc163 I can not change webpack config for some legacy reason,I wish everything is going well like 7.12.18。 |
#12900 shows well what is the problem. I'm sorry that this update broke your project, but it's a problem in you webpack configuration: In the meantime, you could pin |
{
"resolutions": {
"@babel/runtime": "7.12.18",
"@babel/runtime-corejs2": "7.12.18",
"@babel/runtime-corejs3": "7.12.18"
},
} I have locked versions by this way, and the problem is not what you think, and webpack configuration can not be changed in our projects, for some legacy reason those configuration be wrapped like |
The However it was fixed later in some versions between 1.0.0 and 1.0.17: All of the versions mentioned above are 4 years old, when Node.js 6.13 even did not exist. Babel/runtime 7.13 does not support such config, consider upgrade |
@JLHwung Thank you for your suggestion that is really useful, but I did not use |
Can you share a repository with a similar setup that shows the bug? It's hard to reproduce it otherwise. |
I have known the reason that |
_index.mjs
of @babel/runtime@7.13.x may not be resolved for some reason in legacy projects, I would like to recommend babel team to rename_index.mjs
toindex.es.js
, Thanks!The text was updated successfully, but these errors were encountered: