mitosis VS Gatsby

Builder.io Mitosis -

In this case, we combined a fine-tuned LLM, a custom compiler that we wrote, and a custom-trained model.

The heart of Visual Copilot lies in its AI models and a specialized compiler. The initial model, trained with over 2 million data points, transforms flat design structures into code hierarchies. Our open-source compiler, Mitosis, takes this structured hierarchy and compiles it into code. In the final pass, a finely tuned Large Language Model (LLM) refines the code to match your specific framework and styling preferences. This multi-stage process ensures that the generated code is high-quality and tailored to meet the requirements of your project.

Mitosis (https://github.com/BuilderIO/mitosis) is a fantastic project, but is still in its early stages, and in need of some build tooling. It allows you to "write once, run everywhere" in the sense that you can write a UI component and have it compiled to a React component for use in a React project, a Svelte component for use in a Svelte project, and so on. It does not, however, support bundling.

create-multi-lib (run like so `npx create-multi-lib ) is my attempt to contribute a much needed bundling-layer on top of Mitosis.

It also comes with E2E testing included, and your resulting packages include type-declarations.

Depending on your needs, check out Mitosis that let you write components and compile them to svelte, angular, react. https://github.com/BuilderIO/mitosis

Saying that, you could check-out Mitosis.

I see you was inspired by https://github.com/BuilderIO/mitosis was there no way to extend there AST?

I discovered https://github.com/BuilderIO/mitosis, and it has changed my front-end development workflow with the ability to create one development and export and test metrics on multiple front-ends delivering the best MVP possible.

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.