Andrew Branch

> Unfortunately, the consequence of this change is that the `declarationMap` compiler option that is recommended in the OP does not work, because the mapping will go upwards into parent...

Oh, I thought you were referring to your local development workflow with nx, not consuming a package published to npm that was written with nx. I understand now.

Three things: 1. I’m totally sympathetic to this problem; it seems tricky. 2. Copying `.ts` files next to output `.d.ts` files can never ever happen. The `.ts` files have a...

The plan is actually to make that message _less_ prominent: https://github.com/microsoft/vscode/issues/152252 But we can put more info about what happened in the TS Server log.

The problem is that the two "overloads" are identical in signature, and the deprecated one from node is being picked because it was loaded last. If you’re writing DOM code,...

See https://github.com/microsoft/TypeScript/issues/842 for more info. `window.atob()` is a workaround mentioned there.

Hey! I don’t know how I missed the notification for this issue. I don’t have an Upwork account, so I can’t even see the linked profile, but I guess that...

This is expected behavior for TS. Module resolution isn’t affected by whether the importing file has a `.d.ts` or `.ts` extension. I can’t say whether the `paths` approach is correct...

It’s hard to tell without inspecting it myself, but it sounds like `bundles/pixi.js/index.d.ts` may be excluded from the project since it’s an output file, so TS Server isn’t associating it...

I think this cooould be an instance of #41563. It’s essentially an overload selection problem—the intersected `PromiseLike` and `Promise` is a reasonably correct representation of what we know about `p1`,...