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.

Sign up for GitHub

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

Jump to bottom

ESLint Rule import/named for typescript should be disabled #253

Open
Basti237 opened this issue Dec 9, 2022 · 0 comments
Open

ESLint Rule import/named for typescript should be disabled #253

Basti237 opened this issue Dec 9, 2022 · 0 comments
Labels
nuxt2-legacy Issues related to the legacy Nuxt 2 eslint config

Comments

@Basti237
Copy link

Basti237 commented Dec 9, 2022

Regarding the instructions to configure the eslint-plugin-import for typescript @nuxtjs/eslint-config-typescript is not configured correctly because for example the import/named rule is set on error.

This causes ESLint errors in Nuxt projects with Typescript.

Workaround for me is adding these two line to the eslint config

plugin:import/recommended
plugin:import/typescript
@antfu antfu added the nuxt2-legacy Issues related to the legacy Nuxt 2 eslint config label Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
nuxt2-legacy Issues related to the legacy Nuxt 2 eslint config
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Basti237 @antfu