Digests » 116
Learn how it is possible to build a React.js app with Wordpress as a backend with the new WP REST API. Code snippets & live demo included.
this week's favorite
When it comes to structuring a React app, the ideal structure is the one that allows you to move around your code with the least amount of effort. In this post, I’d like to tell you how I structure my React apps, and what drove my decisions. Along the way I’ll mention some options I don’t use because they don’t suit me, but that might serve you well.
React 16 got released. It’s a major release with new features, improvements, performance and more. You can read official release notes or announcement from React team. The official documentation has been updated with a new design (so, it looks a bit different than usual). Below is just a summary of what React 16 release is all about.
Many words, talks and articles have been dedicated to the question “should I be using Redux or MobX?” Even React books tend to discuss both nowadays. Yet there is no ‘winner’ and nor will there be (off-topic: it is even highly questionable if there is anything to ‘win’ in OSS in the first place).
I’d been seeing this other composition pattern on the side for a while. We met initially in some libraries like React Motion and the latest version of React Router. She was very declarative and straight forward. I could read her easily and felt comfortable telling her what I wanted. Not to mention, she was dynamic and flexible, too!
Facebook released a rewrite of a large portion of React last week. React 16 has been much anticipated, and the new Fiber rendering pipeline allows for a lot of performance improvements. While the React team has diligently deprecated methods and packages throughout the last version, warning us strongly in console statements to upgrade, the actual final migration is not trivial for larger codebases. We at Discord just launched our React 16 based app and wanted to share our experience and some tips we learned along the way.