eslint config for nextjs #1322
eslint config for nextjs #1322
Conversation
|
@aymanesarrar is attempting to deploy a commit to the Carbon Team on Vercel. A member of the Team first needs to authorize it. |
|
@aymanesarrar should we update the script to be |
| parserOptions: { | ||
| requireConfigFile: false, | ||
| babelOptions: { | ||
| presets: ['next/babel'], |
There was a problem hiding this comment.
Are we able to remove the various babel/eslint dependencies from our package.json?
There was a problem hiding this comment.
no i don't think we should remove it from our package.json
|
@aymanesarrar |
|
i updated it to next lint and I had a problem that it doesn't know the extends next so I updated it to next/core-web-vitals but It requires to install eslint-next-config I've done it and npm run lint passes with some eslint errors, should i commit ? |
* eslint config for nextjs * removed plugins, settings, parser from the config * changed the script to next lint and installed the eslint next config package * lint fixes * move to dev dependencies * remove unnecessary rules * remove unnecessary babel deps * lint on root dir Co-authored-by: Mike Fix <mrfix84@gmail.com>
The next configuration already handles setting default values for the parser, plugins and settings properties.
more here : https://nextjs.org/docs/basic-features/eslint#migrating-existing-config
Closes #1321