Dokumentation - How to use workspace version
See original GitHub issueIn an Angular-Project, I am trying to replace the TSLint plugin with this plugin.
I am using VS Code Insiders (1.32.0-insider) and I am trying to configure the plugin to use the workspace version of typescript, which is currently 3.2.4.
As the documentation says, that I only need to manually configure the TS Server, if I am using a workspace version in VS Code <= 1.30, all I did was disable the TSLint-Plugin and enable this one.
However, I don’t get any Lint-Warnings.
As soon as I activate VS Code’s typescript version, it works as expected.
So I tryed to install “typescript-tslint-plugin” locally using npm install --save-dev typescript-tslint-plugin
and I even add the plugin
-section to my tsconfig.json
but it still did not work.
Installing it gloablly, using npm install -g typescript-tslint-plugin
did not help either.
Here is the tsserver.log output, without configuring tsconfig.json:
Info 0 [9:27:11.889] Starting TS Server Info 1 [9:27:11.893] Version: 3.2.4 Info 2 [9:27:11.893] Arguments: C:\Users\User\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe c:\Angular\my-app\node_modules\typescript\lib\tsserver.js --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName C:\Users\User\AppData\Local\Temp\vscode-typescript\tscancellation-89a9a45610b753d692c3.tmp* --logVerbosity verbose --logFile c:\Users\User\AppData\Roaming\Code - Insiders\logs\20190211T091343\exthost1\vscode.typescript-language-features\tsserver-log-cu6C3p\tsserver.log --globalPlugins typescript-tslint-plugin --pluginProbeLocations C:\Users\User.vscode-insiders\extensions\ms-vscode.vscode-typescript-tslint-plugin-1.0.0 --npmLocation “C:\Apps\NodeJS\npm.cmd” --locale en --noGetErrOnBackgroundUpdate Info 3 [9:27:11.895] Platform: win32 NodeVersion: 10 CaseSensitive: false
Am I missing something?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
@rodbecc I am using Nx Workspace and my
rulesDirectory
looks like this:Thanks for pointing me to the issue in Nx!
I tryed to remove the
rulesDirectory
for@nrwl/nx
and the plugin works fine now. So this issue can be closed, since it is not an issue with the plugin, but with@nrwl/nx
.