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
If you look close at the browser support, safari did catch up and this looks reasonable to use at this point. The only exception is Firefox for Android, which we can ignore.
With added support for class fields, we can move all configs without a trailing underscore into the class body directly (e.g. className or ntype).
The only downside is, that webpack is not able to build stage3 proposals: webpack/webpack#10216
More precisely: the internal parser (Acorn) needs to get adjusted, which is not possible using webpack based configs.
It feels worth a try. In case we get it working for neo, we could probably get rid of the trailing underscore for configs completely (a breaking change).
The text was updated successfully, but these errors were encountered:
Public class fields are a stage3 proposal for a very long time already:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Public_class_fields
If you look close at the browser support, safari did catch up and this looks reasonable to use at this point. The only exception is Firefox for Android, which we can ignore.
With added support for class fields, we can move all configs without a trailing underscore into the class body directly (e.g. className or ntype).
The only downside is, that webpack is not able to build stage3 proposals:
webpack/webpack#10216
More precisely: the internal parser (Acorn) needs to get adjusted, which is not possible using webpack based configs.
To add support for all (...) stage3 proposals, we could adjust the package.json and add a resolutions prop:
https://github.com/OnurGvnc/acorn-with-stage3
This one only works with yarn. To make it work with npm, we also need to add:
https://github.com/rogeriochaves/npm-force-resolutions
It feels worth a try. In case we get it working for neo, we could probably get rid of the trailing underscore for configs completely (a breaking change).
The text was updated successfully, but these errors were encountered: