tsdx VS Gatsby

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

The first time I started building static websites is when I discovered Gatsby. I built several projects using Gatsby and hosted it on Netlify free tier. It felt like a really robust architecture and I loved that it was free.

A Gatsby site uses Gatsby, which leverages React and GraphQL to create fast and optimized web experiences. Gatsby is often used for building static websites, progressive web apps (PWAs), and even full-blown dynamic web applications.

While Next.js is a powerful framework for building server-rendered React applications, it's not the only option for developers looking to create high-performance websites. One notable alternative is Gatsby, a static site generator that leverages React and GraphQL.

The other piece of important information to acknowledge here is that when we say RSCs need a framework, “framework” effectively just means “Next.js.” There are some smaller frameworks (like Waku) that support RSCs. There are also some larger and more established frameworks (like Redwood) that have plans to support RSCs or (like Gatsby) only support RSCs in beta. We will likely see this change once we get React 19 and RSCs are part of the Stable version. However, for now, Next.js is currently the only framework recommended in the official React docs that supports server components.

GatsbyjsCMS - Gatsby is the fast and flexible framework that makes building websites with any CMS, API, or database fun again. Build and deploy headless websites that drive more traffic, convert better, and earn more revenue!

GatsbyJS

Babel plugins are everywhere. From being used to remove unwanted exports from files in Gatsby to being used to disallow users from doing re-exports in Nextjs.

In terms of GitHub stars, SSGs like Next.js, Hugo, Gatsby, Docusaurus, Nuxt.js, and Jekyll top the list. Some popular SSGs even host conferences and workshops, providing resources and networking opportunities for those looking to explore more advanced topics in depth.

Flexibility : Developers have complete control over the frontend so they can use their preferred tools and frameworks like React, Next.js, Gatsby, or Remix.