Open masakudamatsu opened 3 years ago
A workaround is to delete .eslintrc
and then execute npx next lint
.
This installs eslint-config-next
and create .eslintrc.json
with the following:
{
"extends": "next/core-web-vitals"
}
But it also adds yarn.lock
. Which creates a confusion with package-lock.json
. I'm not sure if it will be fine.
So for the time being, we ignore ESLint.
Deal with this issue alongside #45
Next.js 11 introduces ESLint plugin to flag Web Core Vital issues (source).
But it's not clear how I can revise
.eslintrc
to enable Next.js ESLint plugin...Documentation at https://nextjs.org/docs/basic-features/eslint is not helpful...