hyrious

> Thank you for the suggestion. Are common word missing from the current dictionaries? Yes.. like `transcoding`.

I think you can just change `"import"` to `"default"` if you don't want a CJS copy. Or only enforce the rule at node side: ```json "exports": { ".": { "node":...

I guess this was definitely a hidden issue in svelte itself… My fresh commit: https://github.com/hyrious/esbuild-plugin-svelte/commit/5b8806650dba00f3930637d9b448425d710c2557

This will be very helpful if we can reuse svelte ssr plugin here. Possible implementation: https://github.com/hyrious/esbuild-dev/blob/develop/src/loader.ts [^1] I'm hesitant to add this feature now, since it will be really a...

This is because in ts mode all import names coule be a **type**, esbuild will strip out these names if they are not being used in the code or they...

It seems that the filename `` has some special treatments in esbuild, here's a simple reproduction: ```js import esbuild from "esbuild"; console.log("--- sourcefile: "); await esbuild.build({ stdin: { contents: `import...

Basically 2 things: 1. Constant folding currently does not remove unreachable codes like yours, you can write `if-else` intentionally to make that work: ```diff export function getEntry(name) { if (process.env.BROWSER)...

I'm not sure whether esbuild should treat both `Variable` and `Scope` as just type, because `import A = B.C` can actually be compiled to `const A = B.C`, which may...

> it's invalid TypeScript syntax AFAIK. Yep, I've just updated comments above. So It's hard to say which is right here, maybe babel is wrong too.

FYI, nodejs uses [cjs-module-lexer](https://github.com/nodejs/cjs-module-lexer) to lexically analyze source code to find exports. So we have several choices: 1. Let esbuild annotate more names by analyzing other packages like you said....