Next.js 13
nextjs.org
Next.js 13
1–10 of 106 posts
Re: Next.js 13
#2Awesome 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".
Is it perfect. No. But it's very close for most of my use cases.
Re: Next.js 13
#3All these changes look great. I'm especially glad that next/link always renders an now, if I read it right it seems to solve the "create a dummy span around some imported component" issue.
Re: Next.js 13
#4What 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?
Re: Next.js 13
#5Edit: There's some more discussion about Turbopack at https://news.ycombinator.com/item?id=33333695.
Looks like they launched a webpack alternative called Turbopack today:
> Next.js 13 includes Turbopack, the new Rust-based successor to Webpack.
Re: Next.js 13
#6Turbopack (comes with Next.js 13) seems AMAZING!
> Turbopack updates 10x faster than Vite and 700x faster than Webpack
> Turbopack is an incremental bundler optimized for JavaScript and TypeScript, written in Rust by the creators of Webpack and Next.js at Vercel.
Re: Next.js 13
#7Super excited about Turbopack! Thank you for moving the Web forward so much.
Re: Next.js 13
#8Next[js] Conf is live right now at https://nextjs.org/conf
Re: Next.js 13
#9Edit: There's some more discussion about Turbopack at https://news.ycombinator.com/item?id=33333695 . Looks like they launched a webpack alternative called Turbopack today: > Next.js 13 includes Turbopack, the new Rust-based successor to Webpack. https://vercel.com/blog/turbopack https://turbo.build/pack
Sigh another one? I thought Vite was the new thing.
Re: Next.js 13
#10 // "alt" is now required for improved accessibility