react-hot-loader VS react-fiber-architecture

React Hot Loader - Tweak React components in real time

Developer Experience - There are a number of tools that improves the development experience with React. React Developer Tools is a browser extension that allows you to inspect your component, view and manipulate its props and state. Hot reloading with webpack allows you to view changes to your code in your browser, without you having to refresh the browser. Front end development involves a lot of tweaking code, saving and then refreshing the browser. Hot reloading helps you by eliminating the last step. When there are library updates, Facebook provides codemod scripts to help you migrate your code to the new APIs. This makes the upgrading process relatively pain-free. Kudos to the Facebook team for their dedication in making the development experience with React great.

I am considering how to make my compiler (which outputs JavaScript), output patch changes, which somehow update the server or browser with the code changes, so you don't have to shutdown/restart the server or refresh the page. I was going to take a look at the react-hot-loader source code, but it's a little too abstract, it will take a while / few days at least to start to grok.

I am starting to look through the source of react-hot-loader, but it is no insignificant beast. Can someone explain at a high level how this is implemented, just in enough detail so one could reason about how to reimplement this functionality in another programming language?

[HMR] bundle rebuildingclient.js?3ac5:126 [HMR] bundle rebuilt in 557msprocess-update.js?e13e:27 [HMR] Checking for updates on the server...process-update.js?e13e:81 [HMR] The following modules couldn't be hot updated: (Full reload needed)This is usually because the modules which have changed (and their parents) do not know how to hot reload themselves. See http://webpack.github.io/docs/hot-module-replacement-with-webpack.html for more details.process-update.js?e13e:89 [HMR] - ./src/containers/root.tsxprocess-update.js?e13e:89 [HMR] - ./src/index.tsx I've stepped through these steps as best I can tell, but am still having no luck.

I'm using react-hot-loader and I'm very confused about its example code:

react-hot-loader - Tweak React components in real time

Here is great documentation for you to follow if you are interested in understanding the core concepts.

Can someone remind me why virtual DOM was/is desirable in the first place and why updating the DOM directly is desirable now?

If I understand correctly react elements are created in memory, and only upon "render" it is turned into the actual DOM. Supposedly manipulating the actual DOM is "heavy" hence delay/pruning the virtual DOM tree first then rendering would be beneficial? Then why is it working with DOM directly is desirable? And am I right to assume that "without virtual DOM" means work with DOM directly? Someone in the comment mention that Svelte is without vDOM already. Is there some design document that I can refer to, like the reconciliation engine used in react https://github.com/acdlite/react-fiber-architecture

Перевод статьи Эндрю Кларка “React Fiber Architecture” https://github.com/acdlite/react-fiber-architecture

Over the years, new view libraries that are even more performant than React have emerged. React may not be the fastest library out there, but in terms of the ecosystem, overall usage experience and benefits, it is still one of the greatest. Facebook is also channeling efforts into making React even faster with a rewrite of the underlying reconciliation algorithm. The concepts that React introduced has taught us how to write better code, more maintainable web apps and made us better engineers. We like that.

The concept is a bit complex, but if you're interested in finding out how we might see React in a few years, you can read this documentation from the React page: https://github.com/acdlite/react-fiber-architecture

Fiber is the new reconciliation engine in React 16. Its main goal is to enable incremental rendering of the virtual DOM. This is a complicated concept, basically, this new algorithm is a reimplementation of older versions of the React reconciler, has some improvements on prioritizing the order of how things are rendered, breaks the limits of the call stack, and lets it pause or start rendering work wherever required. You can read more here and here

The result was "Jikji" library (why Jikji? it will need another blog:)) ). It uses React Fiber to get the component hierarchy and reorganized, split, and layout the components before rendering and making a print-ready web view that can easily be printed or converted to PDF or images.

The mechanism to diff one tree with another to determine which parts need to be changed and then update the original DOM with it is called Reconciliation. You can learn about Reconciliation here. ReactJS uses a new reconciliation engine called Fiber since version 16.0. You can read more about the React Fiber Architecture here.