-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Invalid plugin specified in Babel options: "proposal-optional-chaining" #2974
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
Comments
I got the same, showing "Transpiling Modules...". Hours of research, it turns out it's create-react-app causing errors. |
Bump |
Hi 👋 I did some tweaking and was able to make this work: https://codesandbox.io/s/proud-hooks-icp6r
Both of these are workarounds while the parsing logic failed to get the plugin name right, I'm keeping this open as a bug but have fun with optional chaining, such a cool addition! 😄 |
thank you @siddharthkp! I will give it a go. |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
This issue has been automatically closed because there wasn't any activity after the previous notice or the stale label wasn't removed. |
Just ran into this, and can confirm that calling it |
🐛 bug report
Description of the problem
I am trying to use the babel plugin
proposal-optional-chaining
in a custom.babelrc
file. I simply added the depedency@babel/plugin-proposal-optional-chaining
via the Add Dependency button and then I added the@babel/plugin-proposal-optional-chaining
plugin name in theplugins
attribute in the.babelrc
file. Just like the docs stated: https://babeljs.io/docs/en/next/babel-plugin-proposal-optional-chaining.html.However there seems to be a problem detecting the plugin.
How has this issue affected you? What are you trying to accomplish?
Just wanted to play around with the optional chaining proposal
Link to sandbox: link (optional)
https://codesandbox.io/s/headless-http-io6xu
Your Environment
The text was updated successfully, but these errors were encountered: