EVT
react-elm-components
Our great sponsors
EVT | react-elm-components | |
---|---|---|
1 | 1 | |
444 | 778 | |
- | 0.4% | |
7.7 | 3.9 | |
3 months ago | 3 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.
EVT
-
Getting Started with WebSockets in Deno: Tutorial and Examples
The next step will be to instantiate the event emitter that will be used in the API, when we use the dependency evt we can create a totally typesafe client and the only thing we need is define a type and pass it as a generic in the .create() method, like this:
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?
react-i18next - Internationalization for react done right. Using the i18next i18n ecosystem.
react-children-utilities - Extended utils for ⚛️ React.Children data structure that adds recursive filter, map and more methods to iterate nested children.
qrcode.react - A <QRCode/> component for use with React.
reactfire - Hooks, Context Providers, and Components that make it easy to interact with Firebase.
backbone-react-component - A bit of nifty glue that automatically plugs your Backbone models and collections into your React components, on the browser and server
elm-react-component
react-intl-universal - Internationalize React apps. Not only for Component but also for Vanilla JS.
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.
Vest - Vest ✅ Declarative validations framework
react-famous - React bridge to Famo.us
react-faux-dom
react-media - CSS media queries for React