amplify-hosting
amplify-hosting copied to clipboard
aws-amplify
Nuxt.js Server Side Rendering (SSR) support
Is your feature request related to a problem? Please describe. Given the current support for Next.js SSR, I'd like to have a similar option for Vue developers.
Describe the solution you'd like I'd like to deploy Nuxt.js SSR-enabled applications to the Amplify Console.
Additional context
If you're interested in this, please use reactions to šš» the post above!
AWS is misleading in the documentation and giving wrong info
https://aws.amazon.com/about-aws/whats-new/2020/09/amplify-javascript-adds-server-side-rendering-support-frameworks-next-js-nuxt-js/
It is clearly mentiond that AWS Amplify supports NuxtJS with SSR
While AWS Professional support mentioned it is not supported and they even don't have ETA for this feature to be in place ???!!!!
Is there any estimate when this feature is available? Like @sharaola said it's very misleading information in the corresponding blog post / announcement. As far as I can see AWS has to solve this issue by adding some special workflow when detecting a NuxtJS app during deployment, right? I think it's unfortunately not an open source issue the community can solve, correct?
Nuxt3 has moved into public beta, so perhaps the Amplify team can work on supporting Nuxt3. It'd be great to have SSR support by the time it's officially released š¤š»
+1 This will be really helpful when we don't have to handle anything manually except the push of the code so the deployment will be easy and scaling will be also handled automatically.
I might found a way to at least host a Nuxt 3 app via Lambda. Will further investigate and hopefully find a way to host it with Amplify, even it currently doesn't seem to be possible via Amplify Hosting. The creation of a custom Lambda function (in Amplify) might work based on my following solution. Last but not least I can't understand why it seems to be so difficult for the Amplify team to implement Nuxt 3 hosting feature. The community is waiting for ages now and other providers like Vercel are handling it with an awesome user experience instead. To be honest I'm very disappointed about what AWS is (or better is not) doing!
Here comes a possible workaround:
With Nuxt 3 running on Nitro you have the option to build it with deployment presets. It also has one for AWS Lambda called (yes, you guessed it): aws-lambda
- Run
NITRO_PRESET=aws-lambda yarn buildto generate a Lambda compatible version - Zip content of your
.output/serverfolder - Create a new Lambda function (manually via AWS console) and activate function URL feature
- Upload your created ZIP file
- Click on the function URL displayed under your Lambda function ARN
- Et voila, your entire frontend app is server-side rendered on AWS including dynamic routes
Please let me know if you think this might be a temporary workaround to at least host Nuxt 3 apps serverless on AWS or if you have another solution. Cheers!
// Edit: Unfortunately it currently looks like CSS and other assets are not being loaded, even moved into the ZIP file from public directory. Will try to figure out why and keep you posted
I was able to make SSR work by following this https://kodius.com/blog/nuxt-ssr-on-amplify/.
@Batto1300 This is not SSR. It's using the generate command which generates a static site. SSR means it is running a nodeJS instance in the background that handles requests and generates HTML on the server-side.
@bart @cweachock
Give this a look: https://github.com/nuxt/nuxt.js/issues/13478
And this repo: https://github.com/ffxsam/nuxt-sst
Thanks for pointing this out @scalemaildev but unfortunately it doesn't solve the main issue: AWS still doesn't support AWS out of the box whereas other cloud service providers like Vercel do. That's an issue just AWS can solve and they promised it for months now. I accepted that they give a sh*t on Nuxt 3 community and switched to Vercel and Firebase / Supabase with most of my projects.
Thanks for pointing this out @scalemaildev but unfortunately it doesn't solve the main issue: AWS still doesn't support AWS out of the box whereas other cloud service providers like Vercel do. That's an issue just AWS can solve and they promised it for months now. I accepted that they give a sh*t on Nuxt 3 community and switched to Vercel and Firebase / Supabase with most of my projects.
Of Vercel/Firebase/Supabase which would you recommend for someone that wants to run a Nuxt3 app "on the edge"? Specifically, a multiplayer game app with a lot of back and forth between client and server?
@scalemaildev Depends a little on what your server exactly does. If it ist just handling requests and for example generates timestamps Vercel is fine. If you have data that needs to get stored into a database and if you have a more complex app ecosystem I would recommend Firebase which is closer to AWS.
@bart what's the benefit of switching to Vitesse? And vanilla Vitesse or Vitesse+Nuxt3? https://github.com/antfu/vitesse-nuxt3
@dbhagen Main benefit for me is the release date delta between new major versions. It took more than 2 years to update NuxtJS to Vue 3. I don't wanna blame anyone for it because I know that a lot of braking changes took place (for example the new Composition API just to name one here). But in terms of issues we codes have to solve every day there are way more community solution out there for Vue 3 than for Nuxt for sure. Your choice should depend on the project you plan. If it is a single page app only, for sure Nuxt 3 might be the better choice. But if you need a little more freedom and a bigger community (Nuxt is just a piece of the Vue cake) then Vue 3 packed in Vitesse might be the better way to go.
I'm curious if this feature is even being considered? The lack of Nuxt SSR support has brought a major project to a screeching halt as we had operated on the assumption (based on the original announcement) that Amplify would support SSR for Nuxt. Thanks!
Just wanted to update the links in the OP with the latest references:
I'd love to hear if there was any movement on this request! Is it even being considered?
It doesn't seem the Amplify team is really interested in supporting this... too bad
By the time this issue was open I was a young tough developer now Iām retired
