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

41–50 of 113 posts

Re: Next.js 15.1 is unusable outside of Vercel

#41

Post by koakuma-chan »

sali0 wrote: post #35

Next and RSCs have become some of the most frustrating things I've worked with on frontend. Dealing with FE is already annoying enough, but having to wrestle the magic of Next and then vendor lock-in to Vercel to top it off. Team is trying out Tanstack router + vite this week. Excited to build a regular ass CSA.

> Next and RSCs have become some of the most frustrating things I've worked with on frontend

What is frustrating about RSCs? They work really well for me and I'm still using Next.js only because of RSCs.

Re: Next.js 15.1 is unusable outside of Vercel

#42

Post by nonninz »

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?

React Router 7, formerly known as Remix.

Re: Next.js 15.1 is unusable outside of Vercel

#43

Post by throwingrocks »

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.

Remix or React Router + Vite is still great.

Re: Next.js 15.1 is unusable outside of Vercel

#45

Post by miyuru »

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.

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

With whats mentioned in the blog post I would not use it even from static builds.

Re: Next.js 15.1 is unusable outside of Vercel

#47

Post by ImprobableTruth »

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's the issue with the remix -> react-router transition? As far as I can tell it's just a branding thing.

Re: Next.js 15.1 is unusable outside of Vercel

#48

Post by aitchnyu »

jowday wrote: post #28

Don’t ever use Next. Terrible developer experience, vendor lock in, weird undocumented conventions that make building anything other than some kind of B2B SaaS CRUD site full of undocumented foot guns. My favorite thing I’ve encountered is the Next tag somehow dropping the FPS on a webgl scene on the same page to 2 FPS.

How was Vercel able to frog-boil normal React users with vendor lock-in? React was supposed to be Meta's baby and open source was supposed to defeat vendor lock-in.

Re: Next.js 15.1 is unusable outside of Vercel

#49

Post by celicoo »

It's really sad what Next.js has become. I still use it, but I have to maintain my own fork with patches. The next.config.js file is an ugly escape hatch that lets you change default behavior for things that should be properly extensible instead of being hidden behind "feature flags" in the first place. Honestly, the framework is a solid D grade at this point — complete spaghetti code.
Post reply on HN