The biggest update of Next since its release is finally here 🎉. It was presented in style at the Next.js Conf 2022 conference, which I definitely recommend watching. Here are some news:
However, the new version of Next also has several breaking changes, e.g. the minimum version of React has been moved from 17.0.2 to 18.2.0. You can also find everything important on the Next blog.
Now it's time to replace Webpack with Turbopack, also built on Rust. Here are some (marketing) comparisons:
Turbopack will be used in Next.js 13 as a development server, and later it will also provide a production build. You can read everything important on the Vercel blog.
The question is to what extent these are marketing numbers. Evan You, the creator of Vite, wrote a reaction to the first (marketing) benchmarks:
Node.js 18 is in Long-term Support (LTS) 6 months after its release. You can easily develop new applications on the new Node and update older projects. Node.js 18 will be supported until April 2025. The biggest changes are e.g.:
We usually deploy our web applications on a server in one of the large data centers, e.g. in California, Germany... However, the future trend is different. We can already distribute static content around the world closer to users via CDN. However, this trend is also starting for dynamic web applications that you can deploy anywhere in the world. Is the future of the web on the Edge? You can find out on the Deno blog.
Take a few minutes to fill out the survey: State of CSS 2022. In addition to learning about new trends in CSS from the survey, you will also help browser developers prioritize their plans and work on better cross-browser compatibility. Also based on the last survey, browsers have implemented several improvements that have troubled CSS developers until then. You can also read more on the Smashing Magazine portal.
In the article The future of rendering in React, you will read about the current rendering patterns in React, their problems and how the new patterns in React 18 try to solve these problems. Even if they are not currently ready for production, it is good to prepare for them.
If you liked the news overview, don't forget to subscribe to our newsletter. You can also read the news from last month, which we brought in the September Frontend Briefly.