Ron Park

> > Please discuss things in issues before sending a PR. > > What’s your use case where you have that many named imports? Things should be deep-imported from granular...

I wrote an issue for discussion about this 😄 https://github.com/import-js/eslint-plugin-import/issues/2553

# import/named-order Enforce a convention in the order of `import` / `export` / `require()` specifiers +(fixable) The `--fix` option on the [command line] automatically fixes problems reported by this rule....

> I don't think two options like `esmodule/commonjs` are needed like any other rules. Why should they be different? Option names are weird when I look at it again. I...

When importing an external library, I think it is a good direction to import it separately for tree shaking. However, tree shaking is often unnecessary in internal code. In my...

> Why are all 20 of those types coming from the same file? @ljharb It's an off-the-topic part of this discussion, It seems that a lot of interfaces or types...

> > but I guess that it is necessary to have an option to not apply import or export or require for some environment. > > Any real usage case?...

> @ronparkdev I don't think it's off topic - if it's indeed a bad practice to have so many named imports (such that ordering is required), then there's no benefit...

Hi @benjamn, We are also following your recommendation. However, `v3.4.0-beta.22` version also has a memory leak issue, And I found causing a memory leak in useQuery. But, every implement is...

Yes, It should modify to `| React.FC` ```javascript /** * @deprecated as of recent React versions, function components can no * longer be considered 'stateless'. Please use `FunctionComponent` instead. *...