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
Under some obscure ambiguous ava/eslint/lerna/typescript configuration, the tsconfig.json from this package ends up being parsed by the vscode eslint extensions.
This triggers a puzzling eslint parsing error (within vscode only) because of the rightfully missing dependency @sindresorhus/tsconfig
Possible workaround is to include @sindresorhus/tsconfig as a devDependency of the project where the issue occurs.
Another option could be to have the defer-to-connect npm package to only include the necessary files:
A quick follow up in order to document/share the correct solution to the original issue ( parsing error in vscode eslint extension.)
When working on a mono-repo, the vscode eslint extension may find it difficult to determine the correct working directory for each package. This is why the setting eslint.workingDirectories exists.
In my specific case, adding the following .vscode/settings.json to my project ensure vscode eslint extension doesn't mess up:
Under some obscure ambiguous
ava
/eslint
/lerna
/typescript
configuration, thetsconfig.json
from this package ends up being parsed by the vscode eslint extensions.This triggers a puzzling eslint parsing error (within vscode only) because of the rightfully missing dependency
@sindresorhus/tsconfig
Possible workaround is to include
@sindresorhus/tsconfig
as a devDependency of the project where the issue occurs.Another option could be to have the
defer-to-connect
npm package to only include the necessary files:Possible options are:
.npmignore
"files": ["dist"]
inpackage.json
The text was updated successfully, but these errors were encountered: