react-gradual-upgrade-demo
modern-todomvc-vanillajs
Our great sponsors
react-gradual-upgrade-demo | modern-todomvc-vanillajs | |
---|---|---|
9 | 19 | |
420 | 1,063 | |
0.2% | - | |
0.0 | 4.9 | |
over 1 year ago | about 2 months ago | |
JavaScript | CSS | |
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.
react-gradual-upgrade-demo
-
Node module issues when gradually upgrading to React 17 from React 15
I've run into a weird issue when trying to gradually upgrade. If you don't know, React Gradual upgrade is a fun process where you require three package.json's - one in the root directory, one in src/legacy and one in src/modern. Refer to here for more info: GitHub I am getting the errors after running npm start ("webpack-dev-server --hot"):
-
TodoMVC App Written in Vanilla JavaScript
The event listeners get cleaned up by the GC. At least in modern browsers.
While events aren’t explicitly mentioned, MDN offers an insightful read:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Memo...
Alternately, one can use event delegation [0]. As does React under the hood [1].
0 - https://javascript.info/event-delegation
1 - https://reactjs.org/blog/2020/08/10/react-v17-rc.html#change...
-
Enzyme is dead. Now what?
React 17 Release Candidate came out. Shortly after, an issue has been raised in Enzyme repository to add support for React 17. Immediately after, @layershifter has opened a PR adding an official enzyme-adapter-react-17.
-
React 17 runs useEffect cleanup functions asynchronously
Yes, the React core team discussed that in their blog post on the release candidate of v.17, and advised those who really need synchronous cleanup to use the useLayoutEffect.
-
The Plan for React 18
React 17 included quite a bit of that work. Most of the event system was simplified/rewritten, pooling was removed, and delegation moved to the root.
-
React 17 DOM tree inside of React 16.2 DOM
Is it possible to do the reverse of the demo? - https://github.com/reactjs/react-gradual-upgrade-demo/
-
Two versions in the same web app
See https://github.com/reactjs/react-gradual-upgrade-demo
-
React.js 17: No New Features and New JSX Transform
You can take a look at a demo of gradual updates on an example repository put together by the React team.
-
What’s new in React v17.0 ?
Checkout the demo for gradual upgrade.
modern-todomvc-vanillajs
- Writing a TodoMVC App with Vanilla JavaScript in 2022
- Ask HN: Good resource on writing web app with plain JavaScript/HTML/CSS
- Writing a TodoMVC App with Vanilla JavaScript
-
React I Love You, but You're Bringing Me Down
> React takes us forward in the sense that most of us don't want to go back to direct DOM manipulation
There was recently a demo of what a Todo MVC app might look like if written in vanilla JS with today's apis. It looks fairly decent; I could see myself going back to something like that:
https://frontendmasters.com/blog/vanilla-javascript-todomvc/
- Writing a TodoMVC App With Vanilla JS in 2022
-
Ask HN: What happened to vanilla HTML/CSS/JS development?
>> Does not trigger when modified from the same page
I'm thinking that's the purpose of https://github.com/1Marc/todomvc-vanillajs-2022/blob/main/js... - without dispatching that custom save event, there wouldn't be a way to react at any other locations on the same page to the store updating.
- GitHub - 1Marc/todomvc-vanillajs-2022: Vanilla JS TodoMVC App in 2022
- TodoMVC App Written in Vanilla JavaScript