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
Rather than banning particular ES versions or individual features, I'd like to be able to declare the browser features that are to be supported. This might be for this plugin, or some companion plugin/config that works with it.
The es/no-foo rules included in the output config would be dynamic, based on the browsers matching the browserslist spec, looked up against a compatibility database.
I ended up making this myself, as a plugin which delegates to this plugin. It uses browserslist and the MDN browser compatibility data. Also made a companion CLI tool.
I've just released a beta version which covers ES2018 and 2019. It shouldn't be much more work to add the other ES20xx versions for a MVP. Let me know if you have any feedback.
If it turns out well, it may be worth linking to as a related tool.
Thanks for your work on this plugin - it does all the hard work so all I had to do was join everything up.
Rather than banning particular ES versions or individual features, I'd like to be able to declare the browser features that are to be supported. This might be for this plugin, or some companion plugin/config that works with it.
As a starting idea...
The
es/no-foo
rules included in the output config would be dynamic, based on the browsers matching the browserslist spec, looked up against a compatibility database.Leading on from:
The text was updated successfully, but these errors were encountered: