Boshen @boshen.github.io 路 May 20 Is there a resource for publishing dual cjs esm packages, where you mark a subdirectory module type with a package.json file? Here is my understanding, but may be wrong. github.com/oxc-project/...
8 likes 6 replies
Replies
CCing the super pro @acemarke.dev
I've been using this trick for fast-check.dev 馃槄 But not sure where I found it
Multiple package.json files in package subpaths is not a thing, that sounds like a huge misunderstanding of the spec. This is exactly what the export conditions are made for.
nodejs.org/docs/latest/... Not sure if it helps
For a real-world example look at the @babel/runtime package. - it uses cjs by default - in helpers/esm/package.json, it marks files inside helpers/esm as being esm
some of this is the result of tooling iirc some tools produce dual packages by making a 2nd `package.json` for sake of running tsc with the right `type` set. they should clean that up, but it often gets published i may be hallucinating this (maybe im an LLM) but im pretty sure thats where its from