package-publishing

To configure package.json exports for dual ESM and CJS builds, use the `exports` field to define separate entry points for `import` and `require`. This ensures your JavaScript package resolves correctly across different Node.js and browser environments.

The best way to publish a TypeScript npm package is to set the `types` field in `package.json` to point to your generated `.d.ts` files. This ensures consumers of your package automatically receive accurate TypeScript type declarations.

npm package lifecycle scripts like `prepublishOnly` secure the publishing workflow by running automated checks right before the package is uploaded. This prevents accidentally publishing broken builds or incorrect files to the npm registry.

You should use the `files` field in package.json to explicitly whitelist the files included in your published npm package. This prevents unnecessary source files from bloating the package and ensures consumers only download the required ESM and CJS builds.

npm package provenance is a supply-chain security feature that links a published package to its exact build source code. You need it when publishing npm packages to provide downstream consumers with verifiable guarantees about the code origin.

To set up package.json for a JavaScript library, configure `main` for CommonJS entry, `module` for ESM entry, and `types` for TypeScript declarations. This combination ensures maximum compatibility across varied build tools and environments.