Andrew Branch

@Perryvw the thing that makes me most suspicious is that in the TSTL playground, the error appears on the method signature node itself rather than on the bit of the...

Yeah, double checked with the team and it’s definitely not supposed to happen, though I don’t find it too surprising. The call to `getSymbolAtLocation` from `buildLinkParts` in src/services/utilities.ts is the...

@Andarist recently fixed a few related bugs; I’m not sure if this got fixed as a side-effect.

4.2.2 is several versions old. Does it crash with the nightly? https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-typescript-next

The method signature for `then` is ```ts then( onfulfilled?: ((value: T) => TResult1 | PromiseLike) | undefined | null, onrejected?: ((reason: any) => TResult2 | PromiseLike) | undefined | null...

> > Could you generate the new object from the namespace object, creating own enumerable getters for every export to support live bindings, and add the non-enumberable __esModule property to...

@alexander-akait if someone defines the `type` in their loader config, which value gets used? The one I set in this PR or the loader config value?

Just wanted to drop in and say this is still on my radar; just figuring out how to expose the related config in TypeScript itself is proving difficult.

ts-loader is the only bundler scenario I know of that relies on tsc’s emit. For example, it’s conventional when using esbuild to have `noEmit` in your tsconfig. I knew this...

Yeah, something like that—that’s what https://github.com/TypeStrong/ts-loader#faster-builds describes via `fork-ts-checker-webpack-plugin`, but my sense is a lot of people are moving toward just relying on errors in-editor and in CI via a...