Dunqing / typack

What is typack?

typack bundles multiple TypeScript .d.ts entry points into a single declaration file, tree-shaking unused exports and resolving name conflicts semantically. This github native alpha tool, built in Rust on the Oxc parser, skips tsc entirely for native typescript node support, delivering fast CLI, Rust library, and Node.js bindings via npm. Users get source maps, external package handling, and CJS export syntax in one output.

Why is it gaining traction?

It outperforms JS-based bundlers like rollup-plugin-dts (now maintenance mode) with Rust speed and standalone operation—no tsc deps or source file compilation. Key hooks: semantic-level rename accuracy, optional source maps (rare in DTS tools), multi-entry bundling, and native typescript runtime efficiency for CI/build pipelines. Even powers rolldown-plugin-dts under the hood.

Who should use this?

Library authors bundling types for npm packages, especially those with complex inter-module exports or external deps like React. Build tool devs integrating native typescript nodejs bundling into Vite/Rollup/Webpack plugins. Teams ditching slow tsc invocations for github native script workflows.

Verdict

Worth trying for pure .d.ts bundling needs—solid docs, benches, and real-world tests—but at 23 stars and 1.0% credibility, it's early alpha (automerge not enabled). Pairs well with native typescript compiler flows; monitor for stability before prod.

(198 words)