custom-elements-everywhere
mitosis
custom-elements-everywhere | mitosis | |
---|---|---|
19 | 29 | |
1,135 | 10,788 | |
0.5% | 1.0% | |
8.9 | 9.1 | |
6 days ago | 7 days ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
custom-elements-everywhere
-
Unlocking the frontend – a call for standardizing component APIs pt.2
With React (it seems) finally moving to support everything needed (they are the last major framework lagging behind substantially), too, we might be moving to a world post-framework discussions, and real interoperability on a technical level. I think Jake Lazaroff motivates this beautifully with his articles “Web Components Eliminate JavaScript Framework Lock-in” and “The Web Component Success Story”.
-
Use web components for what they’re good at
Seems it doesn’t work in React, everything is sent as a string. There was a link in the article that shows how well web components work with various frameworks.
https://custom-elements-everywhere.com/
You can see how React fares for itself.
-
If Web Components are so great, why am I not using them?
React supports Web Components, just some quirks to be aware of: https://custom-elements-everywhere.com/
-
[AskJS] Asking advice on monorepo setup with multiple frameworks
You could wrap each component as a Web Component and then import them for each repo. Web Components are not native to frameworks, so the support for them could vary when passing props. Or you could wrap the render method of each framework as a function and then use the receiving frameworks life cycle method and inject it onto the page. If you use frameworks like Svelte or Lit that are "Web Component" based, then you'd need to see if the receiving framework supports Web Components inorder to import the seamlessly.
-
Am I the only one that thinks that the direction of React is wrong?
Check compatibility of React with web components: https://custom-elements-everywhere.com/ It's not directly because of jsx, but because of synthetic "let's make it up" approach of React.
-
Regarding converting svelte file into pure js file
I have been using this approach recently as well, working great thus far ! Some things to consider though: - I would recommend checking if the other frameworks you intend to use have good web components support (looking at you, react): https://custom-elements-everywhere.com/ - There are ways to do so without web components, but I wouldn't recommend them unless your framework has poor web components support.
-
HTML with Superpowers: An Introduction to Web Components
VueJS actually fails some advanced tests for WebComponents: https://custom-elements-everywhere.com/
So, VueJS docs are actually incorrect when they say it scores 100%. The actual score is 90%.
I had reported this 8 months ago.
-
Building Web Components 101 - Part 1
Since Web Components are supported natively by browsers, they can be used in any libraries and frameworks either directly or with configurations. https://custom-elements-everywhere.com/ is a great site to check custom elements support status by different libraries and frameworks.
- Check if a library/framework supports the usage of custom elements
- custom-elements-everywhere.com: Check if a library/framework supports the usage of custom elements
mitosis
-
Nx - Highlights of 2023
Builder.io Mitosis -
-
Don’t Build AI Products The Way Everyone Else Is Doing It
In this case, we combined a fine-tuned LLM, a custom compiler that we wrote, and a custom-trained model.
-
Introducing Visual Copilot: A Better Figma-to-Code Workflow
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.
-
Show HN: Create-multi-lib – Write UI code once, compile to multiple frameworks
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.
-
[AskJS] Asking advice on monorepo setup with multiple frameworks
Depending on your needs, check out Mitosis that let you write components and compile them to svelte, angular, react. https://github.com/BuilderIO/mitosis
- Making a case for open-standard base templating syntax to partially unify front-end development
-
[AskJS] best stable free (framework agnostic*) ui library?
Saying that, you could check-out Mitosis.
-
Show HN: Build your own no-code editor with Reka.js
I see you was inspired by https://github.com/BuilderIO/mitosis was there no way to extend there AST?
- Ask HN: Any good ideas Figma to Angular implementation?
-
Best front-end stack for Golang backend
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.
What are some alternatives?
stencil - A toolchain for building scalable, enterprise-ready component systems on top of TypeScript and Web Component standards. Stencil components can be distributed natively to React, Angular, Vue, and traditional web developers from a single, framework-agnostic codebase.
partytown - Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉
details-dialog-element - A modal dialog that's opened with <details>.
html-figma - Builder.io for Figma: AI generation, export to code, import from web
hybrids - Extraordinary JavaScript UI framework with unique declarative and functional architecture
angular-email-editor - Drag-n-Drop Email Editor Component for Angular
feelback-integrations - Feelback SDKs, integrations libraries and samples
tailwind-figma - FlowBite is a free and open-source set of UI components and pages in Figma built for Tailwind CSS
astro - The web framework for content-driven websites. ⭐️ Star to support our work!
web-vitals - Essential metrics for a healthy site.
qwik - Instant-loading web apps, without effort