nx VS tsdx

One notable feature is the ability to remember selected tabs. When you select a specific tab on a page, all other tabs on the page with the same name will also be selected. This selection will persist during your next visit to nx.dev.

Hono does have a template application for Vercel, but in my case, my requirements were different (aren't they always 😅). I was working in a monorepo (using nx) because I wanted to manage my libs, tests, and examples all together in a single place, instead of having different repos.

Recently, My coworker is using Nx to automate his workflow, including automated release using semantic version. I found this method quite useful, so I want to re-implement on single GitHub repositories (without Nx).

I started a discussion on GitHub concerning that subject: Design Nx Plugin Project Crystal

Nx

We are looking for companies to partner with on the Analog project to support development of the project. Thanks to Snyder Technologies for being an early adopter and promoter of Analog, Nx for joining us as a sponsor, House of Angular, and many other backers of the project.

Additionally, thank you to all our community launch partners across the frontend ecosystem for helping us bring Storybook 8 to the world! Thanks to Chromatic, Figma, ViteConf, Omlet, DivRiots, story.to.design, StackBlitz, UXpin, Nx, Mock Service Worker, Anima, Zeplin, zeroheight, kickstartDS, and Kendo UI.

The advent of esbuild, the native support for ES Modules in browsers, the widespread adoption of import map, the emergence of tools like Native Federation, and the Nx ecosystem all combine to forge a flexible and well-maintained Micro Frontend Architecture.

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