Boshen

We need this for the transformer after finishing Milestone 1 @Dunqing

Ok this isn't the right direction, closing again.

@XantreGodlike To be honest I don't really get this rule, and there's so many issues with it https://github.com/search?q=repo%3Aimport-js%2Feslint-plugin-import+no-named-as-default&type=issues But for default exports, you may add a `Option` because you can...

> Hi. To implement this rule, it seems necessary to implement a parser like [@eslint-community/regexpp](https://github.com/eslint-community/regexpp). > > Where is this planned to be implemented? If it's within this repository, please...

> Oops, I forgot to mention one thing. I will try to implement the prototype, but if anyone reading this comment wants to work on this issue, please don't hesitate...

> There is not `new-import-rule` The test cases `eslint-plugin-import`'s aren't static enough for us to convert automatically, all the test cases are ported manually :-(

I want to tackle the list of super slow rules that use `ExportMap` in `eslint-plugin-import`: * default (recommended) * export * named (recommended) * namespace (recommended) * no-cycle * no-deprecated...

To port the tests, we'll need to clone `eslint-plugin-import`, add a console.log to copy the code over. ```javascript console.log("let pass = vec![" + valid.map((test) => `r#\"${test.code.trim()}\"#`).join(',\n') + "];\n") console.log("let fail...

> I created this reward to encourage this issue to be resolved as it hasn't received updates in a long time. Is the reward deleted? Anyway, all work from @leaysgur...

After battling cjs / esm for 3 days ... I'm going to cut the scope and focus on ESM only. i.e. Only lint if the imported file is a ESM...