eslint-plugin-import-x
eslint-plugin-import-x copied to clipboard
un-ts
A fork of `eslint-plugin-import` using `get-tsconfig` to replace `tsconfig-paths` and heavy `typescript` under the hood.
Hi, I recently switched from eslint-plugin-import to this package, thanks for taking over. Most things are drop-in replacements but I'm struggling with `import-x/extensions` in Typescript env. No matter what I'm...
Some 3rd party modules may minify the released files. It would be helpful to add an option to exclude those modules manually. For example, [markdown-it-anchor](https://www.npmjs.com/package/markdown-it-anchor?activeTab=code): Any thoughts? @SukkaW
This PR fixes the false positive with the package "typescript-eslint" and "eslint-plugin-jsdoc". ## Summary by CodeRabbit * **Bug Fixes** * Fixed false positives in the no-rename-default lint rule so legitimate...
Steps to reproduce: ``` git clone [email protected]:un-ts/eslint-plugin-import-x.git cd eslint-plugin-import-x yarn npm run lint ``` This gives the following output: ``` > [email protected] lint > run-p lint:* > [email protected] lint:docs >...
I have a package `lunr` For it, the types `@types/lunr` are installed. The types are added locally to `@types/lunr.d.ts` (also `./@types` added in `tsconfig`'s `compilerOptions.typeRoots`). After that, the package `lunr`...
I use a meta-package to easily install other packages. For example, "foo-metapackage" depends on "foo-1", "foo-2", and "foo-3". So, instead of projects having to depend on "foo-1", "foo-2", and "foo-3",...
From @silverwind: > I think eslint-import-resolver-typescript is currently only mandatory for typescript, but I think we should make it a dependency and default to it for both JS and TS....
Steps to reproduce: ``` git clone [email protected]:un-ts/eslint-plugin-import-x.git cd eslint-plugin-import-x yarn npm run test ``` This gives the following output: https://pastebin.com/ZPjyAgKb More info: I am on a Window 10 machine, using...
I'm using eslint-import-resolver-oxc and it seems `"import-x/resolver": "oxc"` doesn't work, firing `Unable to resolve path to module`, while `"import-x/resolver": { oxc: true }` works as expected. ```javascript languageOptions: { parser:...
