You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The introduction of .eslintrc in blitz-js/blitz#298 broke VSCode/ESLint integration (reproduced on multiple devices).
Steps to Reproduce:
Assuming you had ESLint working in VSCode previously...
Clone Blitz repo (current canary branch as of this issue being logged)
Install dependencies (yarn)
Open in VSCode
Open a file (e.g. packages/core/src/index.ts) and observe lint errors (e.g. Parsing error: The keyword 'export' is reserved)
Delete .eslintrc and the errors go away and integration is restored
Versions:
N/A
Supporting Documentation
The tsdx CLI supports merging .eslintrc.js (don't think it honors .eslintrc though), but that isn't enough for VSCode, which doesn't know to perform said merge (so it only looks at the config it finds, which in this case is missing things like the TS parser, etc.). The solution from tsdx is to "eject" the ESLint config if you need to extend it while retaining editor integration.
The text was updated successfully, but these errors were encountered:
What is the problem?
The introduction of
.eslintrc
in blitz-js/blitz#298 broke VSCode/ESLint integration (reproduced on multiple devices).Steps to Reproduce:
Assuming you had ESLint working in VSCode previously...
canary
branch as of this issue being logged)yarn
)packages/core/src/index.ts
) and observe lint errors (e.g.Parsing error: The keyword 'export' is reserved
).eslintrc
and the errors go away and integration is restoredVersions:
N/A
Supporting Documentation
The tsdx CLI supports merging
.eslintrc.js
(don't think it honors.eslintrc
though), but that isn't enough for VSCode, which doesn't know to perform said merge (so it only looks at the config it finds, which in this case is missing things like the TS parser, etc.). The solution from tsdx is to "eject" the ESLint config if you need to extend it while retaining editor integration.The text was updated successfully, but these errors were encountered: