Edit: There's some more discussion about Turbopack at <a href="https://news.ycombinator.com/item?id=33333695" rel="nofollow">https://news.ycombinator.com/item?id=33333695</a>.<p>Looks like they launched a webpack alternative called Turbopack today:<p>> Next.js 13 includes Turbopack, the new Rust-based successor to Webpack.<p><a href="https://vercel.com/blog/turbopack" rel="nofollow">https://vercel.com/blog/turbopack</a><p><a href="https://turbo.build/pack" rel="nofollow">https://turbo.build/pack</a>
Awesome release. As an early adopter of Next.js and seeing it evolve over the years, it's been one of the most consistent frameworks that continues to get better and "just works".<p>Is it perfect. No. But it's very close for most of my use cases.
<i>Turbopack</i> (comes with Next.js 13) seems <i>AMAZING</i>!<p>> Turbopack updates 10x faster than Vite and 700x faster than Webpack<p>> Turbopack is an incremental bundler optimized for JavaScript and TypeScript, written in Rust by the creators of Webpack and Next.js at Vercel.
I'm pleased to see cumulative layout shift (re self-hosted fonts) advertised as a feature, this is the right kind of user-centric development, indeed the small details like these go a long way in improving user experience.
<p><pre><code> // "alt" is now required for improved accessibility
</code></pre>
I'm all for accessibility, but let us decide when to implement it.
I find the data fetching example extremely confusing…<p>1. Where does this "use" comes from ? It is not present in the official React API reference : <a href="https://reactjs.org/docs/react-api.html" rel="nofollow">https://reactjs.org/docs/react-api.html</a><p>2. It says that the value is not serialized, but what if Page is rendered client side and I want getData to always be executed server side (for example, it may contains secret API key, or make a database call) ?<p>3. getData is async, so what happens to name if the promise is not yet resolved ?
The next-gen bundler rewrites are getting insane, just as things were consolidating in the other parts of JS. We now have:<p>- EsBuild<p>- SWC (also written by someone who works at Vercel)<p>- TurboPack<p>- Vite (rollup)<p>- Parcel<p>- Rome<p>I've noticed in the javascript ecosystem there is much less convergence than in other languages. Everyone wants a flag in the ground.
> <i>With Server Components and nested layouts in Next.js, you're able instantly render parts of the page that do not specifically require data, and show a loading state for parts of the page that are fetching data. With this approach, the user does not have to wait for the entire page to load before they can start interacting with it.</i><p>Crazy huge user win.<p>I am a little nervous how much stuff Next does in the middle, how thoroughly it links front & back end. Streaming a page with chunks missing then streaming sections as they resolve is pretty advanced magic. Amazing DX experience but I also can think back to asp.net & remember huge viewstate blobs & utterly magic middle-layers, and those were powerful too, but impregnible bizarre systems to the developer & that wasnt good.<p>Next keeps hitting reaply really nice sweet spots & consolidates & tackles so many problems, and my trepidation is small at this point, but this is really redefining the page a lot, & I feel like I really want some deep dives on the technics involved here, want to know the magic is somewhat accessible & coherent, for fellow would be meddlers.
I started my journey with Vue, then Nuxt (of course),then switched to React and last year started to use Nextjs. So far I have no complains (at least no big ones).<p>With new frameworks poping out (qwik, remix, fresh, etc...), it's getting really interesting and tiresome at the same time.<p>We're migrating all our platforms to React/Next and we couldn't be happier. Is it perfect? Nothing really is. Next is good enough, the community is engaged, the ecosystem is big, and the industry is basically dominated by react (giving react devs some sort of peace of mind when looking or switching jobs).<p>Sometimes, you have to pick a piece of tech and roll with it as long as the tech keeps improving and the community improves alongside it. Nextjs is currently doing it.
Not knowing anything about the new /app directory support, I'm able to migrate my static landing page in about two hours. The resulting page is definitely smaller and load faster than the previous version. Now I'm consistently getting 100 on page speed insight (mobile) while previously it's hovering around 98-99.<p>The documentation for the new /app directory support is not complete though. API routes seems to be not documented yet (or is it not implemented yet?) so I haven't ported mine and leave it on the /pages/api directory for now.
Their tutorial is incredible, everyone should take a lesson from Vercel on this: <a href="https://nextjs.org/learn/foundations/from-react-to-nextjs/getting-started-with-nextjs" rel="nofollow">https://nextjs.org/learn/foundations/from-react-to-nextjs/ge...</a><p>Tell me:<p>1. What I need to know to understand this documentation<p>2. The before state (plain React.js)<p>3. The after state (Next.js)<p>I'm fucking sold, I'm going to use Next.js just based on how well written this documentation is.
I’ve been trying out the pre-release version for the last couple of months, just published a quick brain dump of my thoughts related to the major changes (router, server components, etc) as they stand today.<p>I’ve already heard from the team about the plan for my last concern, and it seems viable.<p><a href="https://andrewingram.net/posts/thoughts-on-next-13-react-18-3-dynamic-with-some-limits/" rel="nofollow">https://andrewingram.net/posts/thoughts-on-next-13-react-18-...</a>
Surprisingly, my compile times with Next.js 12.3 have been really really awful. A simple CSS change takes almost 10 seconds to compile and I'd love to know why.<p>My app isn't complex, it uses Recoil, Tailwind and that's it. Compile times were better in v11 in my experience.
What i am still missing is the possibility to deploy next.js to a serverless platform where files have to be stored in S3 or Google Cloud Storage.
Had anybody success to get it working, without loosing ISR functionality?
All these changes look great. I'm especially glad that next/link always renders an <a> now, if I read it right it seems to solve the "create a dummy span around some imported component" issue.