recursive-proxy-mock VS tsdx

Let's take a specific example. One of my libraries recursive-proxy-mock is bundled with Rollup. If you take a look at dist/cjs/index.js you can see there is one big file with everything in it, all bundled together. There are named exports for each thing. This can easily have unused code eliminated either via tree shaking or dead code elimination. I've never made a distinction as to which applies in which scenario since both should always be used together. But I guess my point is, a bundled library doesn't need to have any special format which would require a bundlers help to drop dead code.

If you want to check out my build config for my library that sounds very similar in architecture to yours, feel free: https://github.com/CreativeTechGuy/recursive-proxy-mock

Take a look at the recursive-proxy-mock library. The ability to create an object where every property or function "exists" with infinite depth is a really powerful primitive. Not just for providing mock implementations to complex objects for testing, but also for the ability to store and replay operations on another object in the future.

If you are just looking for a TS library config (not related to react) then here's a good example I can share: https://github.com/CreativeTechGuy/recursive-proxy-mock/blob/main/rollup.config.js

tsdx - Zero-config CLI for TypeScript package development

If you’re into TypeScript, I highly recommend https://tsdx.io . I’ve used it to create a package before and it’s so much easier

Thanks for the insight fellas. Aside question, I was thinking of bootstrapping the project with tsdx, but their last release was well over 2 years ago. Wondering if there are any alternative options for creating libraries?

NOTE: If your project uses TypeScript, I would suggest using tsdx instead.

Sadly, it's a bit dead. We switched to dts-cli fork, but tsup looks good too

I don't depend on the actual typescript docs much but thankfully in @types and in tons of repos there are examples of well written typescript code.

The amount of JS and TS out there is also a bit of a foot gun though so stick with heavily used/starred libs if you aren't sure.

One tool that helps a lot with developing libraries in typescript is TSDX[0] or its successor dts-cli[1] and there is a bunch of good stuff in awesesome-typescript[2].

Maybe library devving is harder?(more work?) with tyepscript but it is worth it for the end developer, especially if that end developer is you. If you aren't using your own libs then you're probably getting paid by someone else to make them or... idk.

https://github.com/jaredpalmer/tsdx

We will use a TSDX library - this tool is something similar to create-react-app, but for creating components library. It allows as to initialize a project immediately with already set up bundler, Rollup with Typescript supporting, testing with Jest, code formatter, Prettier and Storybook.

May be you need to try https://tsdx.io/

So what is the ideal way to build TypeScript libraries? I've heard that tsdx https://tsdx.io/ is quite good

There’s tsdx. But I’d recommend using Vite and storybook-vite