kaizen-design-system
react-elm-components
| kaizen-design-system | react-elm-components | |
|---|---|---|
| 2 | 1 | |
| 155 | 778 | |
| 0.0% | 0.1% | |
| 9.6 | 3.9 | |
| 3 days ago | 4 months ago | |
| TypeScript | Elm | |
| MIT License | BSD 3-clause "New" or "Revised" 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.
kaizen-design-system
-
Use TailwindCSS prefixes for shared design system components
For the purposes of this article, shared components are user interface elements that are used in more than one web application. In Culture Amp's case this includes the React components in our Kaizen design system.
-
Why and How We Retired Elm at Culture Amp
https://github.com/cultureamp/kaizen-design-system/blob/3ac2...
react ver:
react-elm-components
-
Why and How We Retired Elm at Culture Amp
They were considered, I was on the team that considered them. (I work at Culture Amp and at one point was leading the Design System team).
To be clear: embedding Elm in React is easy (we host the main NPM library for doing so: https://github.com/cultureamp/react-elm-components). But embedding React in Elm is harder, as Elm doesn't give any easy "escape hatches" to interact with native JS code.
The main opportunity is to use Web Components. Elm knows how to render any HTML component, including `x-my-custom-button`, which could render using React or something else. We looked into options for this, including prototyping https://www.npmjs.com/package/backstitch as a way to embed our React components as Web Components for consumption in Elm. (No open source packages existed to do this at the time).
We also did quite a deep dive on using Stencil, which has a React-like API, to create web components for both React and Elm - even including publishing new plugins for the ecosystem to generate Elm bindings for your web components. Kevin went into some of the detail for this in the post if you're interested.
What are some alternatives?
elm-ts - A porting to TypeScript featuring fp-ts, rxjs6 and React
react-children-utilities - Extended utils for ⚛️ React.Children data structure that adds recursive filter, map and more methods to iterate nested children.
reactfire - Hooks, Context Providers, and Components that make it easy to interact with Firebase.
elm-react-component
react-on-rails - Integration of React + Webpack + Rails + rails/webpacker including server-side rendering of React, enabling a better developer experience and faster client performance.
react-famous - React bridge to Famo.us
react-media - CSS media queries for React
react-lottie-player - Fully declarative React Lottie player
EVT - 💧EventEmitter's typesafe replacement
react-three-renderer
gl-react
react-unity-webgl - React Unity WebGL provides a modern solution for embedding Unity WebGL builds in your React Application while providing advanced APIs for two way communication and interaction between Unity and React.