Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stale eslint-plugin-import@2.26.0 in eslint-config-next@13.x.x #54480

Closed
1 task done
filipjakov opened this issue Aug 24, 2023 · 1 comment · Fixed by #54490
Closed
1 task done

Stale eslint-plugin-import@2.26.0 in eslint-config-next@13.x.x #54480

filipjakov opened this issue Aug 24, 2023 · 1 comment · Fixed by #54490
Labels
bug Issue was opened via the bug report template. Linting Related to `next lint` or ESLint with Next.js. locked

Comments

@filipjakov
Copy link

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
	Platform: darwin
	Arch: arm64
	Version: Darwin Kernel Version 21.6.0: Sat Jun 18 17:07:22 PDT 2022; root:xnu-8020.140.41~1/RELEASE_ARM64_T6000
Binaries:
	Node: 18.17.1
	npm: 9.6.7
	Yarn: 3.2.3
	pnpm: N/A
Relevant packages:
	next: 13.3.0
	eslint-config-next: N/A
	react: 18.2.0
	react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

ESLint (eslint-config-next)

Link to the code that reproduces this issue or a replay of the bug

x

To Reproduce

Try using 'import/no-duplicates': ['warn', { 'prefer-inline': true }], with the latest eslint-config-next

Describe the Bug

Related ticket: import-js/eslint-plugin-import#2863

Trying to add support for typescript's new flag verbatimModuleSyntax.

Since the codebase is big, the idea is to add eslint warning rules for imports and as soon as the developer touches a file, it will --fix its content based on the following rules:

'@typescript-eslint/consistent-type-exports': 'warn',
'@typescript-eslint/consistent-type-imports': 'warn',
'@typescript-eslint/no-import-type-side-effects': 'warn',
'import/no-duplicates': ['warn', { 'prefer-inline': true }],

But since the eslint-plugin-import@2.26.0 is not latest, i get:

Configuration for rule "import/no-duplicates" is invalid: Value {"prefer-inline":true} should NOT have additional properties.

By declaring the import plugin inside my eslint configuration, I get the: Error: Plugin "import" was conflicted between ...

Would it be possible to update the package to LTS?

Expected Behavior

Using 'import/no-duplicates': ['warn', { 'prefer-inline': true }], yields no errors

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

@filipjakov filipjakov added the bug Issue was opened via the bug report template. label Aug 24, 2023
@balazsorban44 balazsorban44 added the Linting Related to `next lint` or ESLint with Next.js. label Aug 24, 2023
@kodiakhq kodiakhq bot closed this as completed in #54490 Aug 25, 2023
kodiakhq bot pushed a commit that referenced this issue Aug 25, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Sep 8, 2023

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot added the locked label Sep 8, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. Linting Related to `next lint` or ESLint with Next.js. locked
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants