Modern exports field defined

Without a modern exports field, Node.js 16+ consumers get inconsistent resolution across bundlers and runtimes. Tools like webpack 5 and Vite treat the exports map as authoritative — packages that rely on legacy main/module fields alone can fail outright under strict resolution or expose internal files via unguarded deep imports. ISO 25010 modifiability and interoperability both degrade when entry points are implicit rather than declared. The practical result: import errors in production that only surface at the consumer's build step, not yours.

Add the exports field to package.json mapping the root entry point with import, require, and types conditions. Keep legacy main, module, and types fields as fallbacks for older tooling.

{
  "exports": {
    ".": {
      "types": "./dist/index.d.ts",
      "import": "./dist/index.mjs",
      "require": "./dist/index.cjs"
    }
  },
  "main": "./dist/index.cjs",
  "module": "./dist/index.mjs",
  "types": "./dist/index.d.ts"
}

Use a build tool like tsup (tsup src/index.ts --format esm,cjs --dts) to generate both formats and the exports map automatically. Verify the referenced files exist in dist/ before publishing.