You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Historically, we only add the `@babel/plugin-proposal-class-properties`
so that we make sure the ordering is right with the decorators proposal
(otherwise, it can end up compiling in the wrong order). With a recent
version of `@babel/preset-env` and, transitively, `caniuse-lite`, this
resulted in cases where we added that plugin but *not* related plugins
for private class properties, which in turn triggered a Babel assertion
about not adding the properties together as appropriate when the caniuse
database (correctly) reported that .
The fix is:
1. Bump to a more recent version of `@babel/preset-env`, which comes
with a correspondingly bumped version of `caniuse-lite`, which in
turn correctly understands what the latest versions of targeted
browsers are.
2. Include in `ember-cli-babel` itself a check for whether we even
*need* to add the plugin, and only provide it when the provided
`targets` indicate that they require it.
Resolves#419
)} has added the class-properties plugin to its build, but ember-cli-babel provides these by default now! You can remove the transforms, or the addon that provided them, such as @ember-decorators/babel-transforms.`
0 commit comments