library-bundler

Bundle your library across multiple formats by configuring a build tool like tsup, Vite, or Rollup to output ESM, CJS, and UMD entry points. Define format-specific outputs in your build config, specify external dependencies to exclude, and generate corresponding type declarations for each format.

Tree-shaking removes unused code when you mark dependencies as external, use ES modules for your source, and configure your bundler to eliminate dead code during minification. Combine this with code splitting to separate concerns and analyze bundle size to identify optimization opportunities.

Yes. Configure your build to generate .d.ts type declaration files during bundling, include them in your npm package, and use package.json exports to point to both JavaScript and type files. Set up npm publishing workflows with versioning, changelog generation, and git tagging for production releases.

Define conditional exports in package.json using the exports field to route import and require requests to separate ESM and CJS bundles. Your bundler outputs both formats, and consumers automatically receive the correct module format based on their import syntax.

Yes. Configure build systems to handle monorepo structures and scoped package names (@org/package), manage internal dependencies as external, and publish multiple scoped packages to npm with individual versioning and changelog tracking.

Perform bundle-size analysis to catch regressions, verify type declarations are generated and valid, check that all external dependencies are correctly configured, run type checking on TypeScript sources, and validate the package structure before pushing git tags and publishing to the npm registry.