3 ms·
Lots of negativity here. I don’t share the sentiment. I have ported one project over to the app router months ago when it was still in beta with zero problems a
by Escapado 3y ago
Lots of negativity here. I don’t share the sentiment. I have ported one project over to the app router months ago when it was still in beta with zero problems and another one is in the works using server actions and drizzle-orm to get end to end type safety. I think it’s a blast.
For those complaining about the feature set growing: I think this is just a question of use-case. At my current gig we are using pretty much everything next has to offer for a fairly sophisticated eCommerce site. If your app has thousands of pages (like product pages) with integration into a dozen micro services, auth, large images everywhere, redirects everywhere for seo purposes, middleware for various purposes, i18n and needs SSG for seo and perf reasons then next offers pretty well thought out solutions for all of that.
I can understand the performance argument but most of that is being worked on and the next team has already shipped lots of improvements in the past. But maybe the things I worked on haven’t reached a scale yet where these things become a bottleneck.
- tough 3y agoThanks for sharing your good sentiment here. I would be happy to talk about NextJS and LLM's and AI if you're up for it. Leaving my email on my profile for some days.
- scrollaway 3y agoYeah overall I like the new app router a lot. The pages structure was a mess. It definitely could be better. They're making a pathing mess with eg. parallel routes but it's not /that/ big of a deal all in all. The problem being that when you rely on file paths for routing, you then end up having to build in all kinds of hacks and conventions in the file paths, which are just... not designed for that, they're just keys to files. But the core of the structure and architecture is sound.
- dbbk 3y agoI just looked into the Server Actions documentation. Why is there a 'use server' inside the action if it's already running on the server? What happens if this is omitted? Why is all of this stuff so opaque? https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions#actions https://nextjs.org/docs/app/building-your-application/data-f...
- beardedetim 3y agoI think, if I'm recalling it correctly, that the component that is defining it in the docs can be either client or server and by marking the functiom as server only, Next knows to do magic.
- dbbk 3y agoNext may know that but developers sure won't.
- TechBro8615 3y agoThis kind of noodley bundling opt-out is also extremely dangerous from a security perspective. I expect there are a lot of Next.js apps leaking code and possibly secrets that should only be available on the server.