-
Notifications
You must be signed in to change notification settings - Fork 47
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
start server with errors #129
Comments
@jiangyh1024 yeah, I've just upgraded to the latest react-scripts and got the same issue. When I added I'm investigating right now |
JFYI, I reproduced the issue after upgrading all the dependencies. Assuming we need to drop node 6 and 8 support and upgrade major version of this plugin, I believe this fix should be coupled with that release, thus it's fine to upgrade internal dependencies here. |
Well, it turned out to be an issue in babel itself. Look at the issue and related PR: babel/babel#12478 I think we should wait for new patch version of babel plugins, but in the meantime you can just specify older version of This is what I did for my project: "devDependencies": {
"@babel/plugin-transform-react-jsx": ">= 7.12 < 7.12.10 || > 7.12.10"
} CC @jiangyh1024 |
Thanks , appreciate it very much
发自我的iPhone
… 在 2020年12月13日,下午8:00,Eugene Zhlobo ***@***.***> 写道:
Well, it turned out to be an issue in babel itself. Look at the issue and related PR: babel/babel#12478
I think we should wait for new patch version of babel plugins, but in the meantime you can just specify older version of @babel/plugin-transform-react-jsx.
This is what I did for my project:
"devDependencies": {
***@***.***/plugin-transform-react-jsx": ">= 7.12 < 7.12.10 || > 7.12.10"
}
CC @jiangyh1024
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
the babel issue looks resolved now |
not sure why
The text was updated successfully, but these errors were encountered: