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
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
Add a setting like "tslint.nodePath" to point to a tslint binary. This is especially helpful in scenarios where you want to make sure the lint errors you see in vscode match what you would get running it from the command line.
The text was updated successfully, but these errors were encountered:
mjbvz
transferred this issue from microsoft/vscode-typescript-tslint-plugin
Mar 8, 2019
I agree with @poelstra . When you have hundreds of projects in your monorepo, you want to minimize the amount of boilerplate that has to be copy+pasted into each project. If we can discover the location of tslint based on tslint.json (e.g. by following the extends property), that's one less setting to manage.
Add a setting like "tslint.nodePath" to point to a tslint binary. This is especially helpful in scenarios where you want to make sure the lint errors you see in vscode match what you would get running it from the command line.
The text was updated successfully, but these errors were encountered: