eslint-plugin-import
eslint-plugin-import copied to clipboard
ESLint plugin with rules that help validate proper imports.
Hi! 👋 Firstly, thanks for your work on this project! 🙂 Today I used [patch-package](https://github.com/ds300/patch-package) to patch `[email protected]` for the project I'm working on. in typescript 'import type' gets dropped...
## Problem Currently, there is no rule within `eslint-plugin-import` to disallow the usage of barrel files. Barrel files, while convenient in certain scenarios, can introduce challenges in larger codebases, leading...
I have following code : ``` const { addCellToRow } = require("./cell-utils.js"); const { setCellValue, findCell, createCell } = require("./cell-utils.js"); ``` Both require are using the same path, and should...
code: ```javascript import fs from 'node:fs/promises'; import os from 'node:os'; import path from 'node:path'; import util from 'node:util'; import { findWorkspacePackagesNoCheck } from '@pnpm/find-workspace-packages'; import consola from 'consola'; import c...
Like `import/consistent-type-specifier-style`, but for exports. Example: ❌ Invalid with `["error", "prefer-top-level"]` ```ts export {Foo, type Bar}; ``` ✅ Valid with `["error", "prefer-top-level"]` ```ts export type {Bar}; export {Foo}; ```
*Feature Request* It would be nice if it was easy to exclude '#' based imports from the "import/extensions" rule, similar to how it is easy to exclude imports from other...
*Feature Request* It would be nice if the import/extensions rule would only complain about a missing extension if adding the extension would still be resolvable. This is only an issue...
Hello! I've upgraded to eslint@9 in my project and have some issues with linting. Linting of import/order errors is different in CLI/vscode. What i'm getting in vscode:  what i...