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

Next.js 10

nextjs.org

Post reply on HN
Print view View original

181–190 of 206 posts

Re: Next.js 10

#181

Post by randomchars »

jayflux wrote: post #171
makeee wrote: post #89

Earlier quoted context omitted.

Next.js does server-rendering and has API routes built-in. No need for Express or Fastify unless you like the DX of those frameworks better.

The Parent parent was talking about if you don’t use Next and want a more sophisticated setup then then those are alternatives. The parent then asked why do you need to integrate [react] with Express and my answer was if you want to do server side (not using Next)

React was not even mentioned in the thread. OP mentioned integration Next with Express, not React.

Using Express and Next together is relatively common (or at least used to be): https://github.com/shdnx/next-express

Re: Next.js 10

#182

Post by gkhartman »

truesy wrote: post #45

I have mixed emotions on this framework. If you're doing a simple project, Next is the best around. Also great for marketing pages, etc. But if you have a more sophisticated app, with an API, page routes that need to toggle based on cookies, etc, then you have to integrate something like Express. I've done this several times with Next, and it just doesn't pay off. I've also tried to use it at work, but it changes rap…

Would a minimalist framework like mithril.js fill that gap? I've had a pretty good experience when using it for some small to mid sized projects. Since its on the simple side, the updates are infrequent and have been pretty painless to keep up with.

Re: Next.js 10

#183

Post by guykdm »

The new image solution is strictly more powerful than anything currently offered. Since they also control the initial rendering of the HTML, they can seamlessly opt to embed an image via a data url.

Re: Next.js 10

#184

Post by dbbk »

fareesh wrote: post #24

Does Next.js do pre-rendering, i.e. if I have a store with 500 products, will it pre-render the HTML (photos, etc.) for all 500 products and serve it as a static request? Or will it assemble the template on the server, send it down to the client and then do some amount of interactivity hydration later on during the page load? What if my store has multicurrency / multilingual versions of all these 500 pages - will it…

> I haven't used a JS framework with server-side rendering in a while - but from what I remember it seemed to add a terribly high TTFB to the overall page load, which negatively impacted SEO.

You can just stick a CDN like Cloudflare in front of your requests, and this issue is resolved.

Re: Next.js 10

#185

Post by sandGorgon »

Vinnl wrote: post #115
sandGorgon wrote: post #107

Nextjs has the dejavu vibe of docker. It is a brilliant framework dragged slowly and inexorably into "platform lock-in". Nextjs has defocused on SSR (which was the original selling point of a server side Reactjs). And all the other cool features only run on Vercel. It is getting next to impossible to deploy Nextjs (with all its features) on GAE for example...or heroku. There are other alternatives to Nextjs that are…

Doesn't it still come with a server that you can just run on Heroku? That's what I'm doing, and although I'm not at v10 yet, I can't recall any major challenges there.

All the server side parts are now deeply linked to Vercel microservices infrastructure.

As a static site, nextjs is probably a little bit more complex than gatsbyjs (with its zillions of fantastic themes)

Re: Next.js 10

#186

Post by swyx »

pier25 wrote: post #10

The big elephant in the room most of these frameworks are missing is partial hydration. Instead of hydrating the whole page, only the interactive parts are hydrated, sending the absolutely minimal JS needed to the client. AFAIK only Marko has this feature today. Since it's developed and used at Ebay they focused on the best SSR+hydration experience from the start. Imba v2 will also have patial hydration (confirmed by…

> only Marko has this feature

not true, Elderjs from the Svelte ecosystem does exactly this

Re: Next.js 10

#187

Post by reactor »

fasteo wrote: post #110
erokar wrote: post #87

Earlier quoted context omitted.

I feel the same way. We've switched from React to Svelte at work. Going back to React would be a step backwards for us, so much feels needlessly overengineered with awkward APIs. React was a great improvement on Angular, but luckily things are still moving forward.

Which UI component library, if any, do you use with Svelte ?

I've had great success with http://ibm.biz/carbon-svelte for one of my side projects.

Re: Next.js 10

#188

Post by pier25 »

benmccann wrote: post #176
pier25 wrote: post #18

Earlier quoted context omitted.

And... Sapper is dead btw. Rich said it recently in a video. The Svelte team is working on the next big thing combining Svelte with Snowpack. The project is called SvelteKit. https://www.youtube.com/watch?v=qSfdtmcZ4d0

"Sapper is dead" is not really accurate. SvelteKit is Sapper + Snowpack and there will be a migration path.

SvelteKit will replace Sapper which will never reach 1.0. Development on Sapper will stop (or probably has already stopped).

Re: Next.js 10

#189

Post by pier25 »

swyx wrote: post #186
pier25 wrote: post #10

The big elephant in the room most of these frameworks are missing is partial hydration. Instead of hydrating the whole page, only the interactive parts are hydrated, sending the absolutely minimal JS needed to the client. AFAIK only Marko has this feature today. Since it's developed and used at Ebay they focused on the best SSR+hydration experience from the start. Imba v2 will also have patial hydration (confirmed by…

> only Marko has this feature not true, Elderjs from the Svelte ecosystem does exactly this

Ah good point!

Re: Next.js 10

#190

Post by Vinnl »

sandGorgon wrote: post #185
Vinnl wrote: post #115

Earlier quoted context omitted.

Doesn't it still come with a server that you can just run on Heroku? That's what I'm doing, and although I'm not at v10 yet, I can't recall any major challenges there.

All the server side parts are now deeply linked to Vercel microservices infrastructure. As a static site, nextjs is probably a little bit more complex than gatsbyjs (with its zillions of fantastic themes)

Is it though? Do you mean that running `next build; next start` as described at [1] no longer works?

[1] https://nextjs.org/docs/deployment#nodejs-server

Post reply on HN