-
Notifications
You must be signed in to change notification settings - Fork 14
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
ES2022 #44
Comments
Blocked until https://eslint-plugin-es.mysticatea.dev/ has support |
Hi @robatwilliams, thanks for the excellent package. The package is what I want! BTW, Is switching valuable for you? |
Thanks for bringing this to my attention. I see the explanation for the fork at mysticatea/eslint-plugin-es#72 I won't be switching now, but I've subscribed to that issue. I would probably switch if/when the original is confirmed as unmaintained (by the author, or through passage of time), and continued maintenance of the fork is seen (the forker in his comment hopes the need for the fork would be temporary). IIRC the author is a member of the core ESLint team. |
Thanks for the explanation. I respect your decision. By the way, it seems the author of eslint-plugin-es has not been active on OSS for a while, though I also know him as the core member. Also, on mysticatea/eslint-plugin-node#300, the fork was born. |
FIY: The ESLint team plans to set up an organization to deal with maintainer issues such as eslint-plugin-es and eslint-plugin-node. I don't know yet when it will be done though. https://github.com/eslint/rfcs/tree/main/designs/2022-community-eslint-org |
Some hope here if eslint-plugin-es moves to the eslint-community organisation mysticatea/eslint-plugin-es#92 |
Unblocked by #56 - now using the fork |
Arbitrary module namespace names - data not yet in BCD |
Released https://github.com/robatwilliams/es-compat/releases/tag/v3.0.0 with ES2022 support and now using eslint-plugin-es-ex FYI @ybiquitous, @ota-meshi |
https://exploringjs.com/impatient-js/ch_new-javascript-features.html#new-in-es2022
The text was updated successfully, but these errors were encountered: