feelback-integrations VS mitosis

Hi, I'm building Feelback, would like an hand to build the svelte integration. I did already for plain JS and React on this SDKs repo.

Are you twilling about internal private docs or internal source but public facing? Because for the latter I’m building Feelback where custom feedback systems can get a grasp on the user perception of the docs as content. I wrote the Case study of Stripe docs where I share some examples.

Hi, just published the technical architecture of Feelback. The article discusses design principles, tradeoffs and tricks used to build the launch architecture of a SAAS.

Hi, I' building a little plugin to add 'Is this page useful?' upvote buttons (with optional feedback) to documentation websites.

Hi, I'm developing several client SDKs for a website plugin, which require some integration with the common UI frameworks like React, Vue, Nextjs, ...

Hi, I made a little plugin to easily add - Like button or Emoji reaction for blog posts - Is this page useful? upvote widgets for documentation pages - Send feedback form to receive advices/error reporting from users

I built a react package on the repository.

Hi would like some feedback on a plugin allowing to receive user feedbacks about your website content. It allows to easily add: - Likes to blog posts - 'Is this page useful?' with up/down votes on documentation pages - Emoji reactions to sections, parts or comments - Send feedback form for tips or error reporting, with custom data

Hi, I'm building client libraries for a website plugin which allows to receive user signals about your website content.

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.