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

ESLint plugin with rules that help validate proper imports.

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

Prior to v2.23, my `webpack.config` which returns a `Promise` worked fine, but now it causes the following errors (LOTS of them): ``` Webpack config returns a `Promise`; that signature is...

enhancement
help wanted
package: resolver/webpack

I have a project that uses `"import/extensions": "never"` however I have hit a case with the new version of the npm module `lit`. It is common to import like this:...

bug
help wanted

Link to where in the code the error message is being generated: https://github.com/import-js/eslint-plugin-import/blob/d8633c35ba7031eb49b2a36b27c82b289f8f85ce/src/rules/no-extraneous-dependencies.js#L106 Image of error output. The error message format is because I'm using [Trunk Check CLI](https://docs.trunk.io/), a superlinter,...

Babel added support for flow enums here: https://github.com/babel/babel/pull/10344 Currently trying to import an enum results in `MyEnum not found in enum-module` They're currently experimental, but should be coming down the...

enhancement
help wanted
flow

Expected: ```ts import { foo } from 'bar' // newline required here declare module '*.foo' { import { type Foo } from 'bar' // no newline required here const content:...

enhancement
help wanted
typescript

![image](https://user-images.githubusercontent.com/1404810/80574033-5db58900-8a01-11ea-8576-bb04267c922c.png) Queries are supported: https://nodejs.org/api/esm.html#esm_url_based_paths Using `[email protected]` and `[email protected]`

bug
help wanted
package: resolver/node

My current config looks like this: ``` "import/order": [ "error", { "groups": ["builtin", "external", "internal", "parent", "sibling", "index", "object", "type"], "pathGroups": [ { "pattern": "react", "group": "external", "position": "before" }...

import/export ordering

The proposal here is to improve this rule and handle inline type modifiers ``` import { type Foo } from 'T'; import { type Bar } from 'T'; //^^^^^^^^^^^^^^^^^^^^ Error:...

enhancement
help wanted
typescript

## Examples ### ✅ Valid with `no-wildcard-export` ```ts export { parseZodIssue } from './parseZodIssue'; ``` ### ❌ Invalid with `no-wildcard-export` ```ts export * from './parseZodIssue'; ``` ## Why? `export *`...

rule proposal

I have been using the following tslint rule: ``` "no-relative-imports": [true, "allow-siblings"], ``` to forbid any relative imports such as `import constants from '../constants'` I am trying to migrate my...

bug
help wanted
typescript