builder VS mitosis

I created my first custom GPT based on the Builder.io docs site, forum, and example projects on github and it can now answer detailed questions with code snippets about integrating Builder.io into your site or app. You can try it here (currently requires a paid ChatGPT plan).

Check out Builder.io’s GitHub repository for more details about its features and community.

I’ve maintained a handful of JavaScript SDKs over the years. And for each one, the question of how exactly to provide support for fetch in a Node environment inevitably comes up. In fact, we just recently had to resolve some issues concerning this in our Builder.io SDKs.

16) https://github.com/builderio/builder

Personally, I would reach for builderIO's React SDK. It's pretty simple to set up and allows you to specify a selection of your own components.

Yes, It is. Builder Github. I think you might have mistaken them for their premium services.

Hmm, I guess it really depends on where you want to go. If you want a basic editor, sure, write your own, but I see you're integrating rows and columns. If you want to match current UX expectations, you gonna spend a shit ton of time to add things like drag and drop ordering, color and spacing controls, etc. If you want to have a full blown editing experience, I'd check out sth. like https://builder.io/ or https://craft.js.org/

We’re excited to announce that the builder.io homepage now achieves a 100/100 score on PageSpeed Insights, even on mobile, since we adopted Qwik.

The founders of builder.io are actively involved and have the right mindset. Swell.is also checks all the boxes and I am happy to bet on these two horses.

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.