Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Allow usage of external tslint npm module #68

Closed
haugerbr opened this issue Feb 16, 2019 · 3 comments
Closed

Allow usage of external tslint npm module #68

haugerbr opened this issue Feb 16, 2019 · 3 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@haugerbr
Copy link
Member

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.

@mjbvz mjbvz transferred this issue from microsoft/vscode-typescript-tslint-plugin Mar 8, 2019
@mjbvz mjbvz added enhancement New feature or request help wanted Extra attention is needed labels Mar 8, 2019
@poelstra
Copy link

poelstra commented Apr 4, 2019

This is somewhat related to https://github.com/Microsoft/vscode-typescript-tslint-plugin/issues/78, which is about automatically walking tsconfig.json extends fields to find the 'right' version of tslint to use.

@octogonz
Copy link

octogonz commented Apr 4, 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.

@haugerbr
Copy link
Member Author

haugerbr commented Oct 1, 2019

I'm going to go ahead and close this since tslint is deprecated in favor of eslint and the eslint plugin supports this already.

@haugerbr haugerbr closed this as completed Oct 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants