What problem does it solve? Configuring a bundler for library publishing involves juggling output formats, type declarations, dependency externalization, and package.json exports, which is error-prone when done by hand. ## Core Features & Use Cases - Multi-Format Library Builds: Configure entry points, output formats (ESM, CJS, IIFE, UMD), targets, platforms, minification, tree shaking, and sourcemaps through tsdown config files or CLI flags. - Type Declarations & Dependency Control: Generate .d.ts files and control bundling with deps.neverBundle, alwaysBundle, onlyBundle, and onlyImport rules. - Framework Recipes & Migration: Set up React, Vue, Solid, Svelte, and WASM library builds, plus migrate existing projects from tsup using tsdown-migrate. - Use Case: You maintain an npm component library and need ESM and CJS outputs with type declarations, externalized React dependencies, and auto-generated package.json exports validated by publint and attw in CI. ## Quick Start Set up tsdown to build my TypeScript library in src/index.ts with ESM and CJS formats, type declarations, and React externalized.