My motivation to write this article
A few weeks ago I built a Next.js application and deployed it on Netlify.
I enjoyed working with Nex...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for the comments @ch3ber @vfulco @codebydex
As you mentioned it's been moving too fast, there's a lack of resources when you face issues, probably they're still developing and improving the App Router itself and its ecosystem. My intention is not to discourage people from using the App Router even because as my first experience working with Next.js I would really like to work with the technology again. I just hope all the issues don't become a bigger barrier to Next's growth to the point people start to give up on using it.
I've also been using nextjs recently, especially after using App Router, and I was so buggered that I felt helpless with very low 3rd party dependency support, I was wondering if I should give up and choose something stupid.
That's pretty typical of my experience on Netlify with anything more advanced than an SPA. Vercel in my experience just works. I'm having similar experiences right now with a Nuxt site and seriously considering just hosting on Vercel and seeing which platform wins.
I've never tried to deploy a Next.js app on Netlify, your post is very helpful, I'll consider all your issues for future deployments on netlify
I am not doubting any issues related to fast innovation with Next but I seriously question Netlify. I have never been a fan. I am currently deploying Next13 with app router (edge runtime enabled) on Cloudflare Pages + Functions (workers) with no issues and quite a pleasant experience. I create my Cloudflare deployments with Pulumi (IaC) and it is really solid in comparison to something like Netlify. I have not used Vercel yet, but I read about their greatness everywhere and I am sure I will try it soon.
They should have waited with server components and just do what remix did.
Ahora me encuentro desplegando una app de next 13 en netlify y la memoria caché no funciona, incluso con Next Runtime
Enfrenté el mismo problema (bien recordado, olvidé mencionar este), tuve que borrar el caché antes de compilar y terminé agregando esto en el comando npm cada vez que corría el build. Es frustrante porque pierdes las ventajas de usar Next.
I'm working on a project and yea the lack of documentation, maturity and resources for the App Router haver been very challenging
next13 has too many moving parts and has moved too fast resulting in a bunch of errors when I tried the app dir on aws amplify. Thanks for the perspective. I've moved back to pages dir.
Made an account here so that I can thank you! You clued me in on what was going on with the "prefetch" with next/link.