4 ms·

I hate Next.js because they make it extremely difficult to deploy an SSR app anywhere except Vercel. You basically have to use the Docker image to deploy your S

by 65 3y ago

I hate Next.js because they make it extremely difficult to deploy an SSR app anywhere except Vercel. You basically have to use the Docker image to deploy your SSR Next.js app. I prefer https://remix.run https://remix.run or https://vike.dev https://vike.dev However, if you just want a static site, Next.js is great.

Aeolun 3y ago
Ooh, looks like I need to check out Vike. It may address all concerns I have with Next :)
- 65 3y ago
  I use it on my personal site. It's great - easy to use and super robust. Hopefully more people use it.
OccamsMirror 3y ago
There's also Astro: https://astro.build/ https://astro.build/ - which admittedly I haven't tried yet but am planning on checking out for my personal site.
- ringofchaos 3y ago
  Astro is great, using it for my blog site and. I have a mono repo setup React SPA and Astro For Blog. I can create a reusable component in React Repo and reuse in Astro blog. You could also write native astro components which are very close to vanilla html css with added benifit of making reusable components and scoped css. And you can also use svelte or vue components.
- pcthrowaway 3y ago
  Another vote for Astro. Honestly, you can use Astro and then still use React if you want. Doing so would be similar to next.js in some ways, though you need to hook up an adapter if you want server-side rendering
jitl 3y ago
What is the challenge you’ve had deploying SSR Next, and how does it relate to docker? I’ve only used it in docker (I like docker), but I haven’t seen anything in about Next that seems docker oriented.
- 65 3y ago
  Because of how Next.JS builds, you can't just deploy it as-is to something like AWS Amplify or Elastic Beanstalk. For example, if you attempt to deploy to Amplify, you'll get a bunch of 503 errors on SSR pages because of Cloudfront permissions. The static pages work fine though. I'm not exactly sure as to why you can't just "npm run start" on a Next.js app on a deployment service like ELB or Amplify. Perhaps because of the extra SWC compiler Next uses for builds? I believe Docker works because you're doing "npm run start" and containerizing Next.js, essentially proxying the server to then serve to the client. Basically running it on localhost. For example, you can run Next.js on EC2 if you want, but you have to proxy the connection to allow the client to connect to it. Again, I'm not an expert as to why exactly it doesn't work - I just know that it doesn't work the same way a simple node app works, which therefore adds a ton of steps involved that don't make it worth it to me.
Inviz 3y ago
What are frameworks that support async components on clientside?
0xblinq 3y ago
Remix is so much better than Next. We moved a project at work and it’s been night and day for us. Not going back.

by 65 3y ago

Aeolun 3y ago

Ooh, looks like I need to check out Vike. It may address all concerns I have with Next :)

65 3y ago
I use it on my personal site. It's great - easy to use and super robust. Hopefully more people use it.

OccamsMirror 3y ago

There's also Astro: https://astro.build/ https://astro.build/ - which admittedly I haven't tried yet but am planning on checking out for my personal site.

ringofchaos 3y ago
Astro is great, using it for my blog site and. I have a mono repo setup React SPA and Astro For Blog. I can create a reusable component in React Repo and reuse in Astro blog. You could also write native astro components which are very close to vanilla html css with added benifit of making reusable components and scoped css. And you can also use svelte or vue components.
pcthrowaway 3y ago
Another vote for Astro. Honestly, you can use Astro and then still use React if you want. Doing so would be similar to next.js in some ways, though you need to hook up an adapter if you want server-side rendering

jitl 3y ago

What is the challenge you’ve had deploying SSR Next, and how does it relate to docker? I’ve only used it in docker (I like docker), but I haven’t seen anything in about Next that seems docker oriented.

65 3y ago
Because of how Next.JS builds, you can't just deploy it as-is to something like AWS Amplify or Elastic Beanstalk. For example, if you attempt to deploy to Amplify, you'll get a bunch of 503 errors on SSR pages because of Cloudfront permissions. The static pages work fine though. I'm not exactly sure as to why you can't just "npm run start" on a Next.js app on a deployment service like ELB or Amplify. Perhaps because of the extra SWC compiler Next uses for builds? I believe Docker works because you're doing "npm run start" and containerizing Next.js, essentially proxying the server to then serve to the client. Basically running it on localhost. For example, you can run Next.js on EC2 if you want, but you have to proxy the connection to allow the client to connect to it. Again, I'm not an expert as to why exactly it doesn't work - I just know that it doesn't work the same way a simple node app works, which therefore adds a ton of steps involved that don't make it worth it to me.

Inviz 3y ago

What are frameworks that support async components on clientside?

0xblinq 3y ago

Remix is so much better than Next. We moved a project at work and it’s been night and day for us. Not going back.