Post

Confused about the `exports` field in package.json? I wrote a guide to break it down and walk you through it! 👉 hirok.io/posts/node-exports-guide

Think it might be worth mentioning in the TS section that types must be first. For example, if you export types + ESM + CJS, the order must be "types, module, default". Also worth maybe mentioning this tool for validation of types + export conditions arethetypeswrong.github.io By @andrewbran.ch

Really good points! I addressed them all - hirok.io/posts/node-e... - hirok.io/posts/node-e... BTW `types` must be nested inside `require` and `import`. Exports with keys types, import, default was the classic mistake everyone made 😵‍💫

Hmm, I've used "types, import, default" and it seemed to work well? It's also used by eg preconstruct.tools Can you elaborate or point me to some resource on why it's wrong?

Which can be correct with the ESM-wrapper-for-CJS pattern, which is what preconstruct.tools does, and is used in large projects like xstate: arethetypeswrong.github.io?p=xstate%405...

Not sure what Preconstruct tools does or what you mean by the ESM-wrapper-for-CJS pattern—I’d need to see the config to comment. Re: xstate It works because types includes nested conditions for ESM & CJS You need separate .d.ts files for each; many mistakenly ship just one

My understanding is that you only need separate types for esm and CJS if you have a default export. Same types work fine otherwise. Also, here is another preconstruct example without nested types that works: arethetypeswrong.github.io?p=xstate-hel... github.com/VanTanev/xst...