Replies: 2 comments 1 reply
-
First of all, when you put When you do So, the
What this means is that However, it does not include basic eslint configs like The eslint config extends that I personally use: extends: [
'eslint:recommended',
'plugin:@typescript-eslint/strict-type-checked',
'plugin:@typescript-eslint/stylistic-type-checked',
'next/core-web-vitals',
'prettier',
],
|
Beta Was this translation helpful? Give feedback.
-
Would be great to get an official response from @vercel. At least currently it seems like installing the required packages for linting typescript is not possible. Trying to add the recommended extends from above results in the following error:
Running the recommended command results in a conflict.
|
Beta Was this translation helpful? Give feedback.
-
Summary
The document says every common eslint config is buildin. But there is no error for duplicated variables by default. The default eslint config is
eslint-config-next
, and the eslint document mentionseslint-config-next
andeslint-plugin-next
. This is really confused me. Can anyone please let me know what's the diferences from them? And what's the real working common eslint config for a nextjs project?Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions