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

1–10 of 113 posts

Re: Next.js 15.1 is unusable outside of Vercel

#2

Post by dimitrisnl »

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!

Re: Next.js 15.1 is unusable outside of Vercel

#3

Post by dimitrisnl »

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!

Another follow-up. Some libraries[1] started to break from 15.1.8 onwards, so you had to downgrade to the vulnerable versions the author mentioned as well.

[1]: https://github.com/hashicorp/next-mdx-remote/issues/488

Re: Next.js 15.1 is unusable outside of Vercel

#4

Post by drag0s »

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.

Re: Next.js 15.1 is unusable outside of Vercel

#5

Post by ekojs »

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.

Re: Next.js 15.1 is unusable outside of Vercel

#7

Post by Zealotux »

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.

You probably have better alternatives for that: Astro, React Router 7, TanStack.

Re: Next.js 15.1 is unusable outside of Vercel

#8

Post by skyeto »

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.

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

Re: Next.js 15.1 is unusable outside of Vercel

#10

Post by woutr_be »

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 moved away from Next.js, and switched to Astro. Originally I just wanted to go back to basics, but didn't want to bother with having to set up all my routes, templating, serving static assets, build tasks. Astro just handles all that, and it's SSR by default.

I also feel that Astro uses React/Vue as it was intended, as an interactive layer on top of HTML. It also made me realize how little I needed JS frameworks to begin with.

Next just started to feel like to much magic, the server actions felt weird, and just lots of things that required the "NextJS way".

Post reply on HN