Closed Jimmyzm closed 7 months ago
Hi @Jimmyzm !
I think this problem is caused by typescript-eslint
, not @nuxt/eslint-config
.
Better to look for issues on the typescript-eslint
side about the coexistence of typescript-eslint@6.x(@typescript-eslint/*@6.x)
と@typescript-eslint/*@7.x(not typescript-eslint@7.x)
You might come across some hints.
Also, since typescript-eslint@v7.x
is a separate package, it might be better to ask them to check whether they are referring to @typescript-eslint/*@v7.x
or typescript-eslint@v7.x
.
Below is the announcement about v7 of typescript-eslint. You may find a solution here.
https://typescript-eslint.io/blog/announcing-typescript-eslint-v7/
@shinGangan Thanks for the reply, what I mean is the @typescript-eslint/eslint-plugin
package. I just found this Link. It said that The best course of action in this case is to wait until your dependency releases a new version with support for our latest versions. So is there any schedule for upgrading to the latest @typescript-eslint/eslint-plugin
?
Please can we update to v7. A dependancy of v6 is currently throwing an annoying error on every lint:
Here is my eslint config:
At first I just thought
@nuxt/eslint-config
was config-only for eslint, but when I upgradetypescript-eslint
to v7, the eslint started to report error:I just found
@nuxt/eslint-config
containedtypescript-eslint@6.x
, what should I do if I want to use bothtypescript-eslint@v7
and@nuxt/eslint-config
?