ts-sdk-author

To configure dual ESM and CJS build outputs for a TypeScript npm package, use a bundler like tsdown to generate separate output directories and emit .d.mts/.d.cts declaration files for multi-runtime consumers.

The best way to structure a TypeScript SDK public API in a pnpm monorepo is to define enforceable module boundaries by re-exporting public interfaces from a dedicated `src/api` directory while keeping internal implementation files unexported.

Setting up package.json exports for a TypeScript SDK involves creating an export condition map that resolves dual ESM and CJS outputs and includes isomorphic runtime conditions for browser and Node.js environments.

Managing alpha, beta, and rc prerelease lifecycles for an npm package requires using changesets to transition prerelease versions and applying npm dist-tags to isolate and distribute prerelease channels safely.

To verify TypeScript SDK packaging before publishing to npm, wire publint for package.json exports validation and attw for type-resolution checks directly into the `prepublishOnly` npm script.

Yes, you can use Turborepo pipelines for caching TypeScript SDK builds in a monorepo by configuring the pipeline to cache tsdown bundling outputs, generation of .d.mts/.d.cts declarations, and package verification steps.