I've spent some time last couple of weeks to upgrade our codebase to React-Redux v6. Here's a bit of what I've learned, hoping to serve as migration guide :]
"Upgrading to React-Redux v6: Around the New Context API" by @wgao19#DEVcommunitydev.to/wgao19/upgrading-to-r…
We couldn't be more excited to announce... #ReactJSGirls Conference! 👩💻
A conference for every @reactjs
developer, where women take the stage - 3 May in London. 🇬🇧
CFP is already open here: reactjsgirls.com/
🎉🎉 Releasing support for the css prop in create-react-app! 🎉🎉
Go from zero to a new React app styled with the css prop in less than fifteen seconds! 😱😱😱
👉 medium.com/styled-components…
This issue is related to concurrent rendering, context, code splitting reducers and server rendering all at once. It is one of the trickiest issues I've had the pleasure of thinking about and it just keeps evolving.
Thanks @acemarke for dragging me in by tweeting about it!
React-Redux v6 changes behavior around actions dispatched while mounting, because all components still see the original state during that first render.
Seems this breaks dynamically-loaded components+reducers in SSR:
github.com/reduxjs/react-red…
Not sure I have any good ideas atm.
napkin math- the average dev stays at a gig for ~2-3 yrs, and the average dev team doubles in size every 2-3 yrs. so, in 3 years, ~75% (or more?) of the team is "new"/weren't around for the context/arch decisions. so I ask you - what convention/tools/arch could last after that?
🌀 It’s Friday again, time for your weekly dose of React Core and React DOM.
🏞 New Server Rendering Infra: Fizz
🔥 WIP: Base Implementation of React Fire
🐶 Automated Fixture Tests
⚛️️ ... and more!
Subscribe at this-week-in-react.org and read more in the thread below. 👇
I just got my experimental React server renderer working with Suspense data fetching and hooks. Not intended to become anything real and still a lot of work before I can show even the experiment off, but it's fun to play with!
🎉🎉🎉 Spectrum is now part of GitHub!! 🎉🎉🎉
I joined @superbryntendo and @brian_lovin’s quest to build Spectrum because I needed a space for my open source communities.
I’m SO pumped to work on the future of Spectrum as part of the GitHub team!! 😍🎉
spectrum.chat/spectrum/gener…
We wrote a roadmap for the next React 16.x releases! You might have heard about "Hooks", "Suspense", and "Concurrent Mode" from our talks. This post clarifies how they relate to each other and when they'll be ready to use. reactjs.org/blog/2018/11/27/…
Interesting note about the attack: The malicious code only exists in the minified version of the package. Even if you audit your entire dependency graph that wouldn't have helped, unless you also audited all the minified code.
Among others, nodemon is one of the packages with the malicious package in its dependency graph, so check it out if you are using it, but many, many other packages has it too.
People have been warning about these kinds of attacks and how easy they would be to pull off for a long while now. The one that pops to mind:
hackernoon.com/im-harvesting…
Malicious code trying to steal bitcoin found in a very commonly used npm-package. Points the finger to what a fragile world we live in.
github.com/dominictarr/event…
Parts of the problem space reminds me of working with shared data between threads, with potential race conditions etc.
I really admire the React team for trying to abstract that complexity into a predictable and easy to use API, not a trivial thing to do. 💪👏
This RFC describes very well what is still unsolved for the Suspense data caching(/fetching) story, and why it is such a tough problem.
TL;DR: Coordinating a cache across different phases in multiple concurrent roots is really complex..
Something we haven't communicated well is the unfinishedness of the story around data caching. I've opened an RFC to describe the problem space.
Be warned! This proposal is very early stage. It's not unlikely we'll end up with something totally different. github.com/reactjs/rfcs/pull…
💡A really great way to start a new job is to volunteer to write tests:
✅ There are never enough tests
✅ Coworkers will be grateful
✅ Learn the codebase
✅ You can't break anything
✅ You will learn things you didn't know about product
✅ Future you will thank you