publint VS esm-env

Creating npm packages can be challenging. We've seen many tools in this domain, and I encourage you to try dnt. With dnt, I was finally able to pass the package.json linter, which is no small achievement (try jotai, redux, vite).

Only regret is not mentioning https://publint.dev which is similar in many ways (and also great -> just didn't know about it at the time). Maybe we gotta find the publint people/person and do an episode with them??

There are many quirks related to this however, for example if you use "types" it should always be the first entry in your exports, and if you use "default" it should always be the last entry in your exports. Package exports are easy to mess up, and get wrong. Thankfully, there's a really nice project called publint that helps you with things like these.

Not currently, but missing deps is planned under https://github.com/bluwy/publint/issues/13 which should be doable once the infrastructure is done. Deprecated dependencies are probably out of scope for now as that package could technically still work, and it avoids a fetch to npm.

Tools however can use custom keys here as well, like "types", "browser", "development", or "production". This is nice, because it means tools can easily distinguish between environments without having to rely on process.env; this is how esm-env cleverly utilizes package exports to distinguish between development and production environments;

This could help https://github.com/benmccann/esm-env