add-export

Context

Subpath exports are defined in package.json under the exports field. Each subpath maps to a source entry point that gets compiled to dist/. The exports catalog in CLAUDE.md/AGENTS.md must stay in sync with package.json.

The build uses tsconfig.build.json (not tsconfig.json) with rootDir: ./src and include: ["src/**/*"]. This means every source file at src/foo/bar.ts compiles to dist/foo/bar.js — the dist/ path in each export entry must match wherever tsc produces the compiled output for the named source file. Choose your source file location to produce the dist/ path you want in the export entry.

Steps

1. Create the entry point source file under src/ (e.g., src/utils/new-util.ts)

2. Add the subpath to package.json exports, mirroring the source path:

   // source: src/utils/new-util.ts → dist: dist/utils/new-util.js
   "./newutil": {
     "types": "./dist/utils/new-util.d.ts",
     "import": "./dist/utils/new-util.js"
   }
   

3. Update the exports catalog in both CLAUDE.md and AGENTS.md — add a row to the table. These files must stay byte-identical; the simplest approach is cp CLAUDE.md AGENTS.md after editing

4. Build with bun run build to generate dist/ output

5. Verify the export resolves through the package's exports map:

   # Confirm the compiled file exists at the expected dist path
   ls dist/utils/new-util.js
   
   # Confirm the subpath export resolves correctly (tests the exports map, not just the dist file)
   bun -e "import('@cyanheads/mcp-ts-core/newutil').then(m => console.log(Object.keys(m)))"
   

6. Run bun run devcheck to verify

Naming conventions

Checklist

• Source entry point file created with JSDoc header
• Subpath added to package.json exports with types and import conditions
• Exports catalog updated in both CLAUDE.md and AGENTS.md (must be byte-identical)
• If the new export has optional peer dependencies: entries added to both peerDependencies and peerDependenciesMeta in package.json
• bun run build succeeds
• Compiled file exists at expected dist/ path and subpath import resolves correctly
• Integration test at tests/integration/package-consumer.int.test.ts updated: new subpath added to the import spec list and toHaveLength count incremented
• bun run devcheck passes