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

Next.js 12

nextjs.org

Post reply on HN
Print view View original

221–230 of 293 posts

Re: Next.js 12

#221

Post by Zababa »

jekude wrote: post #139
Zababa wrote: post #120

Earlier quoted context omitted.

> 4) A bit too opinionated on DB/Auth (maybe I don't want to use Postgres) This feels like a weird criticism considering Next is React only.

I think your criticism of my criticism is fair. Perhaps this is somewhere you simply cannot provide a clean abstraction and need to be opinionated.

I think that's the case. On the other hand, at a very large scale you may want to move out from Postgres while React can still be fine. I'm not sure if people change more often frontend frameworks or databases.

Re: Next.js 12

#222

Post by acemarke »

dstaley wrote: post #215
acemarke wrote: post #162

Earlier quoted context omitted.

I actually upgraded my team's Jest config to use https://github.com/Brooooooklyn/swc-node a few weeks ago. However, our Jenkins CI agents run RHEL7, and neither of the Linux binary targets would run. The `x64-gnu` binary needed a `GLIBC_2_23` symbol when only 2.18 was available, and the `x64-musl` binary had no `musl-libc` on the machine. I don't own the Jenkins agents, so I couldn't install other deps myself. I ende…

`objdump -T node_modules/@next/swc-linux-x64-gnu/next-swc.linux-x64-gnu.node | grep GLIBC_` Looks like the highest version of `GLIBC` is 2.18, so I think you'll be fine!

Great, thanks for the info!

Already added a story to investigate the upgrade from Next 11 to 12.

Re: Next.js 12

#223

Post by leotaku »

leerob wrote: post #178
leotaku wrote: post #115

Earlier quoted context omitted.

I'm personally curious how the Next is able to achieve the claim of "zero client-side JavaScript" mentioned here[1] using react server components? It just doesn't seem to make sense to me, and the HN clone example and my barebones test project also clearly still load about 74.2 KB of JavaScript. Is the claim supposed to mean that the server components won't require additional JS, or maybe that they won't need to exec…

You can read more here on the original RSC announcement: https://reactjs.org/blog/2020/12/21/data-fetching-with-react... . RSC are still experimental, and as mentioned, this demo has some client-side functionality (upvotes).

Thank you for your response! However, the linked content further seems to support my suspicion that having websites without any client-side JS is not in the scope of RSCs. The linked RFC, in my opinion, clearly states for it to be expected that a client-side framework and React accept and handle the streamed React response[1]. So while it may be possible to eliminate a lot of client-side JS, at least those would always have to be available on the client, correct?

I would also like to make it understood that I'm not here to bash the Next project, I am simply interested in the technology.

[1]: https://github.com/josephsavona/rfcs/blob/server-components/...

Re: Next.js 12

#225

Post by tunesmith »

Rauchg wrote: post #137
CGamesPlay wrote: post #83

I don't want to hate on Next, because I do like using the framework, but a new major version every 5 months for the lifetime of the project? How does anybody actually develop an application when you have to spend so much time keeping your framework up to date?

Stories like this[1] are not uncommon: > One of our users upgraded from Next.js 2.0-beta to 11 in 5 minutes. > As @timneutkens said in the Q&A, Next.js incrementally improving without breaking changes is worth the investment. If this is not the case, please let us know. We try to be very careful around this, and always leave breadcrumbs for easy upgrades in the DX if we absolutely must change something to move the pr…

This was not our experience earlier this year. We experienced a sequence of breaking changes in various dot-releases that led us to not being able to upgrade from 10.0.6 until 11.0.1 came out. Basically every single release in the 10.1.x and 10.2.x lines were unusable for us. We're very cautious about upgrading now.

It's part of why I suggested this issue:

https://github.com/vercel/next.js/issues/26827

Re: Next.js 12

#226

Post by CosmicShadow »

Some exciting stuff for sure, but the most exciting stuff we still have to wait on as it's all experimental until React is ready.

Anything that speeds things up and gives us more control is great though.

Re: Next.js 12

#228

Post by snarkypixel »

burggraf wrote: post #153
gherkinnn wrote: post #92

Earlier quoted context omitted.

Vercel does come with a Supabase integration: https://vercel.com/integrations/supabase And from my limited understanding, Supabase is psql with extras.

Supabase developer here. Supabase gives you full PostgreSQL access as well as a REST api interface (Postgrest) with integrated authentication (based on GoTrue), S3-based storage also integrated to authentication and integrated with your PostgreSQL instance, an easy dashboard interface and a bunch more. There’s a generous free tier and a hosted option that’s ready to scale immediately. Let us know if you have any more…

I tried supabase and went with another solution because it didn't have a good dev/stage/prod system

Re: Next.js 12

#229

Post by revskill »

Rauchg wrote: post #71
capableweb wrote: post #3

Nice, a completely new attack-vector: https://nextjs.org/blog/next-12#url-imports Documentation still not there, so can't check if they actually compare any checksums or anything. They also introduce their own `next.lock` which supposedly new tooling have to built around as well. Versioning management? What, we don't need that for where we're going. Finally it's fun to see it ending with: > We set out to build a zero…

The introduction of Middleware is specifically in alignment with our zero-config principle. You should be able to open `pages/` and understand exactly the flow of traffic. You'll open `pages/`, find `_middleware.js` which processes your request first, and then the rest of the routes. No magic, and heavily inspired in successful predecessors like Express.js. Always open for feedback, let me know if this makes sense!

How to compose middleware then ?

Re: Next.js 12

#230

Post by mariushn »

brillout wrote: post #227

Shameless plug: https://vite-plugin-ssr.com a do-one-thing-do-it-well alternative to Next.js which is feature-complete & stable (no breaking changes in the foreseeable future).

Looks good! Why did you decide to do your own Filesystem Routing instead of introducing a dependency to vite-plugin-pages, especially as you mention upstream contributions?
Post reply on HN