-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[Bug]: Unknown option: .assumptions. #13452
Comments
Hey @rhoehener! 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." |
Do you have multiple |
I only see one such folder.
|
As you can see, the
Update: It seems that |
Ok thank you for looking at this. I will pass it on to Expo and MobX. |
Looks like we can close this? On our end, maybe we want to add a suggestion to check version numbers and when an option was added (or that link could be enough) |
💻
How are you using Babel?
with Expo
Input code
Configuration file name
babel.config.js
Configuration
Current and expected behavior
error when running
expo start -c
Environment
Possible solution
No response
Additional context
Tried to follow https://babeljs.io/docs/en/babel-plugin-proposal-decorators
It says:
When using the legacy: true mode, the setPublicClassFields assumption must be enabled to support the @babel/plugin-proposal-decorators.
The text was updated successfully, but these errors were encountered: