Closed leslee-glints closed 11 months ago
Same issue here. Any thoughts?
@froko @leslee-glints This is an issue with @rushstack/eslint-patch. An issue has been created on their repository page. In the meantime, you can find the fix explained in issue https://github.com/idahogurl/vs-code-prettier-eslint/issues/72.
@froko @leslee-glints @idahogurl i fixed this issue and got it merged into eslint-patch. it is now available on the latest version of the package ("@rushstack/eslint-patch": "^1.3.2"
).
unfortunately i cant reach the nextjs devs to have them upgrade the package version in their eslint extension.
good news though is you can override it.
in your package.json
add this:
"overrides": {
"@rushstack/eslint-patch": "^1.3.2"
}
then run npm i / yarn
to update the package. quit and reopen vscode and you should be good to go.
This issue is stale because it has been open for 14 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
In NextJs Project, it has an open box
.eslint.json
with it eslint convention.I followed the config vscode-prettier-eslint setting process, but not work.
The error output will show like below
I've tried many ways to make it work, and I found that if the
extends
used onlyeslint:recommended
, it work.However, it seems not a good solution by removing the
next
eslint convention.So, how can I config the
.eslintrc
withinnext
to make the vscode-prettier-eslint work well ?Example Project
In my team, we use vercel nextJs admin as the startup project
Screenshots
Versions (please complete the following information):
System Specifications (please complete the following information):