-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Rethink / Reconsider / Revamp Babel presets #13149
Comments
I tried to reproduce this but I couldn't. Did you do this in an app you migrated to version 3, or was it in an app created with Meteor 3 already? Do you have the steps for reproduction? |
Hi @denihs this is a project migrated to version 3 through each version since aroudn 2.5. Those notifications are generated by NPM (npm WARN) so I guess the Meteor version is less important. https://www.npmjs.com/package/@babel/plugin-proposal-class-properties I think what needs to be done is to implement the more official Babel way which depends on |
I can confirm I had the same issue today. @denihs you can ask me how to reproduce it as well |
I have identified two distinct issues from your message @paulincai. 1 - Dependency on Deprecated Packages: The 2 - Legacy vs Modern Browser Compatibility: There's a challenge with Meteor's handling of modern versus legacy browsers. Specifically, there's an issue where Meteor's legacy browser detection incorrectly identifies modern browsers as "legacy". There is already reported issues around this topic that also suggest a solution on mark any new or unrecognized bundle as modern by default. #12177 / #13126 For the moment we have covered a fix on the (1) and fix the deprecations, #13171 |
Screen generated with a Meteor 3-rc.1 project with
meteor npm update
:The text was updated successfully, but these errors were encountered: