Andrew Branch

At a glance, it looks like Webpack’s `module.d.ts` is never referenced from its `"types"` entrypoint. I assume that’s intentional, to prevent those globals from showing up in Webpack config files...

Yes, my memory is that Webpack used to ship without any types and this package was a necessity. It now seems redundant. I agree that this PR is fine, but...

@manuth I can’t quite replicate that issue. This definition seems to be valid with both v8 and v9: ```ts import { PromptModule } from "inquirer"; declare function askName(name: string, inquirer:...

FYI that issue would be fixed by https://github.com/microsoft/TypeScript/issues/49721; you may want to track it.

@evanw I’m pretty sure your examples above will “just work” unless we explicitly disallow them, and I don’t see an immediate reason to do that. The syntax above would certainly...

@DanielRosenwasser should this actually be milestoned right now? It’s a bit hard to tell the status of the spec change, but it looks kinda stuck.

@DanielRosenwasser do we want to make this Help Wanted for 4.6? Kind of surprised we don’t have a community PR already 😁

You are welcome to give it a try by following the process in https://github.com/microsoft/TypeScript/blob/main/CONTRIBUTING.md, but I have no idea how challenging it will be, and we may not be able...

Yeah, if you expand the details, you can see the problem. ``` fileName: "/node_modules/csv-parse/dist/cjs/sync.d.cts" moduleSpecifier: "./index.js" ``` but that directory doesn’t contain an index.js; it contains an index.cjs. https://unpkg.com/browse/[email protected]/dist/cjs/

That feature exists purely on the VS Code side; they don’t ask TypeScript for any info to make that happen.