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
{{ message }}
This repository has been archived by the owner on Oct 28, 2020. It is now read-only.
It would be really cool to be able to test your entire code and then see a small status at the bottom: "Your code will run on 95% of all browsers". If you change one feature it will run on 98%.
The data could be compared to caniuse-lite database to see exactly what features are used by browsers.
Why Is This Update Needed?
Just testing against es6 is not enough, some browsers only have partial support. It would be really useful to have exact statistics of where our code will run and what can we do to make it run on even more browsers without using babel, maybe we are just using one weird feature which we can manually replace ourselves.
Are There Examples Of This Requested Update Elsewhere?
I don't think so.
Read about references issues here. Provide paragraph text responses to each header.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Requested Update
It would be really cool to be able to test your entire code and then see a small status at the bottom: "Your code will run on 95% of all browsers". If you change one feature it will run on 98%.
The data could be compared to caniuse-lite database to see exactly what features are used by browsers.
Why Is This Update Needed?
Just testing against es6 is not enough, some browsers only have partial support. It would be really useful to have exact statistics of where our code will run and what can we do to make it run on even more browsers without using babel, maybe we are just using one weird feature which we can manually replace ourselves.
Are There Examples Of This Requested Update Elsewhere?
I don't think so.
The text was updated successfully, but these errors were encountered: