Andrew Branch

Haven’t looked at the code yet, but from the description, I will note that ```js exports.a = "a"; ``` is more common than ```js module.exports.a = "a"; ``` in my...

> people browsing emitted JS in node_modules This contingency will likely be harmed by the removal of any require/exports-related analysis, unfortunately.

@alan910127 your repo link above 404s—did you accidentally make it private? If you share the repo, I’ll investigate. @Andarist is right; the import you listed as your expected behavior should...

A couple questions: > Another issue is how types extending chai Now, I do not like adding "chai": "

Minimal repro without other libraries: ```ts import https from 'node:https'; export const createServer = () => { return https.createServer(); } ``` (The failure in express-zod-api is unrelated to express)

> ```js > // The declarations in webcodecs.generated.d.ts have been generated using the code in > // https://github.com/yume-chan/webcodecs-lib-generator. See > // https://github.com/yume-chan/webcodecs-lib-generator/blob/main/README.md for more detail. > ``` @dumbmoron were your...

@typescript-bot pack this

@typescript-bot pack this

Yes. Plain `require` calls aren’t recognized as special in TS files. You’ll notice in JS that `require("./foo")` performs module resolution (the compiler knows the type to return), but in TS,...

> We probably should look at if JSR does the same transforms that we're looking to do. From https://jsr.io/docs/publishing-packages#jsr-package-rules, it looks like JSR doesn’t support publishing code that references itself...