Distributing the Transform API as a standalone package

I'd like to suggest separating the Transform API into its own npm package.

esbuild's distribution size is around 10MB, which may be due to features like the CLI, bundler, builder, watcher, and server. The Transform API alone might have a significantly smaller footprint.

Many tools rely on esbuild solely for transformations without requiring other esbuild functionality. Separating this API could reduce disk usage and install time across npm installations, benefiting the ecosystem and users who only need transformations.

I understand this may introduce a maintenance burden and may not align with esbuild's compiled Go-based architecture. Still, I'd appreciate any insights on whether such a separation might be feasible and beneficial.

Thank you!

The issue does not name any files, tests, or entry points. Start by reviewing esbuild's Transform API and how its Go-based distribution is packaged, then determine whether a standalone npm package is feasible and what functionality it would contain. Done would require an agreed design and implementation plan, not just a local edit.

Written by the indexing model from the issue text.