eslint-plugin-import-x icon indicating copy to clipboard operation
eslint-plugin-import-x copied to clipboard

A fork of `eslint-plugin-import` using `get-tsconfig` to replace `tsconfig-paths` and heavy `typescript` under the hood.

Results 102 eslint-plugin-import-x issues
Sort by recently updated
recently updated
newest added

I'm using Next.js. There are conventions of named exports or default exports in certain file names that are not imported anywhere else. I would like to use the `import-x/no-unused-modules` rule...

Removed SublimeLinter-eslint section in the README. This is greatly outdated information, that is marked to be no longer relevant after Eslint 2.0 is released, which happened 10 years ago and...

Hello! Im having the following issue when using VSCode with Eslint and Import-x. I'm opening this issue here because this is the only package where the issue arises, all other...

upstream

cc @nzakas @mdjermanovic @ljharb @JounQin Context: https://github.com/eslint/eslint/pull/19794 **TL; DR** With multi-thread ESLint workers, the existing cache mechanism for one of the biggest performance overheads of both `eslint-plugin-import` and `eslint-plugin-import-x` will...

I'm running with ``` 'import-x/extensions': ['error', 'ignorePackages', { fix: true }], ``` I have many index imports to files like e.g. `/api/index.js` which are currently imported as `import '@/api'`. When...

## ESLint config ```js import { defineConfig } from 'eslint/config' import pluginImportX from 'eslint-plugin-import-x' export default defineConfig([ { plugins: { 'import-x': pluginImportX, }, rules: { 'import-x/newline-after-import': 'error', }, }, ])...

Closes #402. > [!IMPORTANT] > In `extensions.ts`, `fix()` now throws an error with a message if `replaceImportPath()` fails to change the import path, aiding debugging. > > - **Behavior**: >...

# Description The autofixer for the `import-x/extensions` rule does not seem to work out of the box on v4.16.1. # Reproduction Copy paste the following into a terminal. (I think...

enhancement
question
feature

I've ended up down a bit of a rabbit hole trying to get `eslint-plugin-import-x` working in VSCode. I'm consistently getting this error when I introduce `eslint-plugin-import-x`: > Error: Cannot find...

`eslint-plugin-import-x` does not resolve arrays in `imports` correctly. It gives different result from the TypeScript compiler. **`package.json`**: ```json ... "imports": { "#subpath/*": [ "src/subpath/*.ts", "src/subpath/*/index.ts" ] }, ... ``` **`tsconfig.json`**:...