Huáng Jùnliàng

For those interested, here is my brief explanation about this issue: https://github.com/Intellicode/eslint-plugin-react-native/pull/314#issuecomment-1156553355

Babel's maintainer here. https://github.com/Intellicode/eslint-plugin-react-native/blob/4b7149ea7019d288d6318dfabb05461f3134a975/lib/rules/no-raw-text.js#L52-L53 I am worried by the usage of `@babel/traverse` here: - we are passing the ESLint scope to Babel's traverse. - we are not respecting the ESLint...

> what's interesting is that you can make the cjs imported class instantiation as "slow" as esm by using a named import: import { CJSClass } from './cjs.cjs' Named import...

@nzakas I go with a single spec, like we did in Babel. Maintaining a diff between different ES versions is a bit overhead. Can we tag certain commit with `es2015`,...

I think the step 1, 3, 4 is not necessary. > Create a GitHub project that tracks the stage of each ES proposal (so, stages 1-4). This can be updated...

> see the status in a much clearer form with links to any PRs, the underlying TC39 spec The https://github.com/estree/estree/tree/master/experimental serves well, the underlying TC39 spec is linked from each...

> it's possible we'll drop as entirely. Yeah the AST spec tries to cover all the mentioned syntax. If we drop some features when the proposal gets advanced, we can...

IMO an AST should not differ semantically equivalent codes, such as `import {} from 'mod'` vs `import from 'mod'`, and we have more such examples: ```js // single binding arrows...

> The type of Literal of ES2020 is same as type of ES5 Yes, this is how we extend current AST nodes. I don't think it violates the principle of...

It seems to me https://github.com/babel/babel/pull/14666 should be part of this PR, but that one is pending https://github.com/tc39/ecma262/pull/2417#discussion_r896041328. I think we intend to allow `@foo.#bar` as decorator but not `@#bar`. @pzuraq...