morphdom
awesome-react-renderer
Our great sponsors
morphdom | awesome-react-renderer | |
---|---|---|
13 | 7 | |
3,091 | 1,860 | |
- | - | |
4.2 | 4.0 | |
9 days ago | 10 days ago | |
JavaScript | ||
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.
morphdom
-
HTML Streaming and DOM Diffing Algorithm
morphdom
-
The Ultimate Search for Rails - Episode 1
And sure enough, it works! So what's going on here? Well, clicking the link invokes our reflex, which gets executed right before our current controller action runs again. It allows us to execute any kind of server-side logic, as well as play with the DOM in various ways, but with ruby code. Then, the DOM gets morphed over the wire.
-
Build a JS Framework with 80 lines of Javascript
It's super simple actually. And that is in large part to (Morphdom)[https://github.com/patrick-steele-idem/morphdom] which I'm using to compare the output of render() to what is already on the DOM. Morphdom will patch the differences.
-
Using hotwired/turbo but patch the DOM vs Replacing
I'm using morphdom to patch our DOM. Its a very simple library that compares two DOM elements and updates only the differences. It is extremely performant and does not even use a Virtual DOM, just the DOM you already have!
-
Turbo 7.2: A guide to Custom Turbo Stream Actions
using HTML-diffing libraries like morphdom to efficiently update elements on the page
-
how do i morph an entire html document dom?
no it actually looks like morphdom is what i'm looking for.
-
ssceng demo: Hacker News Client
It tries to morph into existing DOM (with https://github.com/patrick-steele-idem/morphdom). In case of fail, there is fallback to HTML replacement with outerHTML. All DOM operations after action occurs on component level, not the whole page.
-
Building a Live Search Experience with StimulusReflex and Ruby on Rails
Today, we’re going to build a live search experience once more. This time with StimulusReflex, a “new way to craft modern, reactive web interface with Ruby on Rails”. StimulusReflex relies on WebSockets to pass events from the browser to Rails, and back again, and uses morphdom to make efficient updates on the client-side.
-
Displaying Real-Time Data in Your Web Application Without Hassle: IHP Auto Refresh ✨
Whenever the JavaScript on the browser-side receives new HTML, it will update the current page using a DOM-diff approach (using morphdom). So only DOM nodes that have actually changed between the initial page load and the updated HTML will be updated.
-
Why Virtual DOM is considered faster that directly updating the real DOM.
Updating the DOM is not slow. In fact, there are libraries and frameworks that emphatically reject the virtual dom approach. morphdom is one such example of a DOM modification library. Svelte's author Rich Harris has been proclaiming for a while that virtual dom is an overhead (see e.g. this article). Google's lit-html and lit-element do much of what react does without the virtual dom.
awesome-react-renderer
-
Interview with Senior JavaScript Developer 2024 [video]
Yes, the reactions to it were not very enthusiastic as you'd expect. Also it did have a11y issues.
There are a lot of interesting renderers for react, some of them are even maintained: https://github.com/chentsulin/awesome-react-renderer
-
nvim-react: ReactJS like UI framework for Neovim (WIP)
Cool work! But title is indeed misleading :( It's because what you've presented is indeed possible with react and js as they're quite versatile, look at this awesome list for examples: https://github.com/chentsulin/awesome-react-renderer
-
Why would we need React without ReactDOM library?
There is a lot of them https://github.com/chentsulin/awesome-react-renderer
-
Why did react chose virtual DOM instead of using real DOM, when other frameworks are more fast even after using real DOM?
For example, because I know React, I was able to code a 3D application that uses ThreeJS and place 3D objects on the screen instead of divs, using the same methodologies just like in a normal web app. You can see other rendering targets at https://github.com/chentsulin/awesome-react-renderer. There are some pretty interesting ones out there.
-
Why Virtual DOM is considered faster that directly updating the real DOM.
List of custom renderers
-
Starter using Vite + React + TypeScript + Tailwind CSS.
Due to its awesome renderer system, there are many React Renderor. So React can be not used only Web, for example, used by React Native.
- Awesome React Renderer
What are some alternatives?
turbo - The speed of a single-page web application without having to write any JavaScript
soprano.nvim - Play soprano music in neovim
Phoenix - Peace of mind from prototype to production
vite - Next generation frontend tooling. It's fast!
hotwire-rails - Use Hotwire in your Ruby on Rails app
Tailwind CSS - A utility-first CSS framework for rapid UI development.
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces. [Moved to: https://github.com/solidui/solid]
react-pdf - 📄 Create PDF files using React
intercooler-js - Making AJAX as easy as anchor tags
nvim-react - Reactive UI framework for neovim
turbo - Incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust – including Turbopack and Turborepo.
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.