-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Scrape more ECMAScript specifications #893
Comments
@Josh-Cena, would you have any interest in implementing this upstream in the |
Yes, I'll try. This is very, very hard, because many proposals are outdated and don't use the standard spec format (for example, they may use a diff format). |
Different formats can definitely be annoying -- I see that one of them even uses an API spec format (https://tc39.es/source-map-spec/)! Thank you very much, though, @Josh-Cena! Let us know if we can help out, I'd be more than happy to submit PRs to assist with this! |
Thanks sooo much @Josh-Cena! |
FWIW, I also manually manage a list of stage-3 specs: https://github.com/jc-verse/mdn-checker/blob/master/packages/mdn-checker/src/data/stage-3.ts |
We currently only get to know about new ECMAScript builtins when they appear in the main ECMAScript spec. We also need to take into account Intl, proposals, and more.
The web-specs package can be helpful to find all of them:
Currently outputs:
The text was updated successfully, but these errors were encountered: