-
-
Notifications
You must be signed in to change notification settings - Fork 451
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
babel-loader@9.1.0 - C-style commenting in JavaScript function calls is causing compilation errors. babel-loader is treating /* comments */ as unexpected tokens when they appear after => arrow functions operators. #972
Comments
same problem |
you can see this explained here diegomura/react-pdf#2072 |
same problem |
We will release a fix for this today. As a workaround, you can pin your @babel/generator version to 7.19 |
but i dont use @babel/generator in my project @nicolo-ribaudo |
not working |
love you, you save me a lot of time @knuula <3 |
Duplicate of babel/babel#15132, this issue has been fixed in |
I'm submitting a bug report
Webpack Version:
5.64.4
Babel Core Version:
7.16.0
Babel Loader Version:
9.1.0
Please tell us about your environment:
Windows 10
Current behavior:
during the compiling process, babel-loader is treating /* */ (C-style comment syntax) as unexpected tokens - causing a compiler failure.
Expected/desired behavior:
babel-loader should treat this type of commenting as normal commenting during the compiling process.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem along with a gist/jsbin of your webpack configuration.
What is the expected behavior?
babel-loader should treat this type of commenting as normal commenting during the compiling process.
What is the motivation / use case for changing the behavior?
it is causing compiler failures.
The text was updated successfully, but these errors were encountered: