This repository was archived by the owner on Oct 16, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 73
Diagnostics are different from those produced by calling tsc
directly
#621
Comments
When I directly interact with
But looking at the process hierarchy, I see that
|
One final data point. If I swap out
|
wincent
added a commit
to wincent/wincent
that referenced
this issue
Jul 21, 2019
Because I am having problems with the diagnostics it shows in Vim not agreeing with what I get from `tsc` or `tsserver` on the command-line, as described here: sourcegraph/javascript-typescript-langserver#621 The confusing naming here drives me crazy, but what is happening in this commit is moving from: - NPM package: javascript-typescript-langserver v2.11.3 - Executable: `javascript-typescript-stdio` (related variant of `javascript-typescript-langserver`, also included with the package) - Package page: https://www.npmjs.com/package/javascript-typescript-langserver (1,171 weekly downloads) - GitHub page: https://github.com/sourcegraph/javascript-typescript-langserver (596 stars) to: - NPM package: typescript-language-server v0.3.8 - Executable: `typescript-language-server --stdio` - Package page: https://www.npmjs.com/package/typescript-language-server (4,175 weekly downloads) - GitHub page: https://github.com/theia-ide/typescript-language-server (166 stars)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In this project I see some puzzling differences between the diagnostics reported by:
tsc
(from typescript 3.5.3)tsc
will report a clean build, but javascript-typescript-langserver complains in this file thatArgument of type 'Iterable<T> | null | undefined' is not assignable to parameter of type 'ReadonlyArray<T> | null...
.There are two
SetConstructor
overloads:Evidently,
tsc
alone is picking the former, but in the context of javascript-typescript-langserver, it's picking the latter, leading to the diagnostic.If I turn debug logging on in LanguageClient-neovim, I get this.
And logging with
--trace --logfil some-file
tojavascript-typescript-stdio
I get this.I don't know if this is related to #618 — perhaps it is not picking up my tsconfig.json. But I don't know if this is a bug in my own code, in TypeScript, in javascript-typescript-langserver, in LanguageClient-neovim, or maybe something else I am overlooking. One thing I did notice was that when I tried to repro in VSCode, it had the same problem, but when I updated it, the problem resolved; the release notes said:
The text was updated successfully, but these errors were encountered: