Explore >> Select a destination
|
You are here 
|
react.dev | ||
| | | | |
www.joshwcomeau.com
|
|
| | | | | This year, the React team unveiled something they've been quietly researching for years: an official way to run React components exclusively on the server. This is a significant paradigm shift, and it's caused a whole lot of confusion in the React community. In this tutorial, we'll explore this new world, and build an intuition for how it works, and how we can take advantage of it. | |
| | | | |
www.trevorlasn.com
|
|
| | | | | How I use the 'Three Layers of Data' architecture pattern for React and Next.js apps to avoid common pitfalls, tech debt, and improve performance | |
| | | | |
mayank.co
|
|
| | | | | Evaluating Next.js's implementation of React's new server features. | |
| | | | |
www.2ality.com
|
|
| | | Rich Harris' module bundler Rollup popularized an important feature in the JavaScript world: tree-shaking, excluding unused exports from bundles. Rollup depends on the static structure of ES6 modules (imports and exports can't be changed at runtime) to detect which exports are unused. Tree-shaking for webpack is currently in beta. This blog post explains how it works. The project we are going to examine is on GitHub: tree-shaking-demo | ||
