Microbundle VS tsdx

I would recommend starting by using https://github.com/developit/microbundle , as it has pretty good default behavior for generating library output.

Check out microbundle, which is what TSDX started as a typescript alternative to.

I’m quite happy with Microbundle

Pick up Microbundle or something similar.

Lerna Microbundle Next.js

Build it with https://github.com/developit/microbundle and save yourself hours of build tooling setup.

Online, on the other hand, the few guides I did find for instance in the microbundle issues have a structure like this:

Since I'm still new to SvelteKit and Vite, though, I still have to figure out the best way to package it for production use, and am coming back to you guys for some tips. Someone recommended I check out microbundle last time around, which I will definitely do, but I'm also curious on other build pipelines, since the one I have right now doesn't really play nice with Vite.

Checkout microbundle. It offers zero-config support for TypeScript, and produces ESM, CJS, UMD, etc.

TSDX is no longer maintained - but it was really nice! Is there any project out there that does something similar?

My company has a component library that we package up with tsdx, publish to our org's GitHub package registry, and consume in various applications. The library makes some use of icons from a package called @icons/material. Until recently, all icons were used by importing a default export, like:

The origin story of TurboRepo started with this looongstanding open issue on TSDX from Nate Moore:

TSDX is a great package for npm packages like this and even bundles with size-limit to check your gzipped final bundle size. Keeping a tiny package was really important to me so there are 0 dependencies and size-limit made me realise that simplifying all of my checking functions into 1 or 2 core functions that took options would be a better strategy and help reduce the code size.

At first i thought that this was THE solution but looking deeper at the source code, this tool is a wrapper around a wrapper around a wrapper.... Don't get me wrong, it probably works, but it's currently using a rollup configuration that was created in 2018, the package itself has not seen any updates in 17 months and has 106 open issues. Also the owner says himself that he's not able to work that much on it anymore and suggest to use TSDX which in return hasn't been updated in several months, many open issues and extensive customization is recommended with patch-package which already in itself is a red-flag :(

tsdx - Zero-config CLI for TypeScript package development

I've had luck with https://tsdx.io/ for a component library. It's really easy to use and was able to publish to npm (self hosted nexus) pretty seemlessly!

Be aware of this discussion. It appears that this library is not maintained actively. I migrated few of my libraries to dts-cli (it is a fork of tsdx)

I've used https://tsdx.io/ recently to get started on a design system. It's real easy to get up and running, even has a template with storybook included

Did you ever tried TSDX?