Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Next.js 15.1 is unusable outside of Vercel

omarabid.com

Post reply on HN
Print view View original

11–20 of 113 posts

Re: Next.js 15.1 is unusable outside of Vercel

#11

Post by csomar »

ekojs wrote: post #5
dimitrisnl wrote: post #2

Oof. I'm sure Vercel might patch this issue. But I had had enough of these little annoyances. For example, the documented way to identify prefetches in the middleware has been broken for weeks (months?). A lot of small issues that keep adding up. I'm not going to shill something else here, but I have a bit of Next.js fatigue lately. Still love the JS ecosystem though. Anyway, thanks for bringing this up!

I share the sentiment. I think we will only be using Next.js for static sites/prebuilt SPA in the future.

Actually Next.js with App router (and with Pages being pushed out) is really bad for SPAs. See this thread: https://github.com/vercel/next.js/discussions/64660

Re: Next.js 15.1 is unusable outside of Vercel

#12

Post by dimitrisnl »

drag0s wrote: post #4
dimitrisnl wrote: post #2

Oof. I'm sure Vercel might patch this issue. But I had had enough of these little annoyances. For example, the documented way to identify prefetches in the middleware has been broken for weeks (months?). A lot of small issues that keep adding up. I'm not going to shill something else here, but I have a bit of Next.js fatigue lately. Still love the JS ecosystem though. Anyway, thanks for bringing this up!

I'm still using Next.js in my work and projects because I still think it may be the best way to ship React to production, but it used to be something fun, enjoyable and productive. sometimes I feel a bit sad about the direction it's going in since the move from pages to the app router.

The best way to ship React to production is with Vite. It opens up tons of options (Tanstack, RR, Simple SPA, whatever) and you don't even bring the hosting provider into the discussion.

Re: Next.js 15.1 is unusable outside of Vercel

#13

Post by dimitrisnl »

skyeto wrote: post #8
drag0s wrote: post #4

Earlier quoted context omitted.

I'm still using Next.js in my work and projects because I still think it may be the best way to ship React to production, but it used to be something fun, enjoyable and productive. sometimes I feel a bit sad about the direction it's going in since the move from pages to the app router.

Curious, anything specific that you'd highlight compared to a setup like Remix that make it easier to ship with Next?

Well, they have consistent naming for a start.

Re: Next.js 15.1 is unusable outside of Vercel

#14

Post by koakuma-chan »

skyeto wrote: post #8
drag0s wrote: post #4

Earlier quoted context omitted.

I'm still using Next.js in my work and projects because I still think it may be the best way to ship React to production, but it used to be something fun, enjoyable and productive. sometimes I feel a bit sad about the direction it's going in since the move from pages to the app router.

Curious, anything specific that you'd highlight compared to a setup like Remix that make it easier to ship with Next?

RSC

Re: Next.js 15.1 is unusable outside of Vercel

#17

Post by freeqaz »

Aeolun wrote: post #16

Next has become a joke. It’s mildly frustrating that with Remix’s inexplicable transformation into react-router, there’s few great react frameworks left (for me), I’m back to plain vite with tanstack router.

What are the best alternatives? Why Vite?

I use Next for a handful of small projects, and SEO was always touted as the big benefit to me.

I can just generate a bunch of static files, copy to S3, and be done. Is that not true anymore?

Re: Next.js 15.1 is unusable outside of Vercel

#18

Post by input_sh »

freeqaz wrote: post #17
Aeolun wrote: post #16

Next has become a joke. It’s mildly frustrating that with Remix’s inexplicable transformation into react-router, there’s few great react frameworks left (for me), I’m back to plain vite with tanstack router.

What are the best alternatives? Why Vite? I use Next for a handful of small projects, and SEO was always touted as the big benefit to me. I can just generate a bunch of static files, copy to S3, and be done. Is that not true anymore?

Have you tried reading the article? It specifically addresses your SEO question.

Re: Next.js 15.1 is unusable outside of Vercel

#19

Post by EspadaV9 »

Aeolun wrote: post #16

Next has become a joke. It’s mildly frustrating that with Remix’s inexplicable transformation into react-router, there’s few great react frameworks left (for me), I’m back to plain vite with tanstack router.

I've been trying and learning TanStack Router with a new project and it's been really nice, so nice that I then added TanStack Query, and then also added TanStack Form.
Post reply on HN