-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuxt 3 SSR Constuct - or Generic SSR Construct as base? #2314
Comments
With the generic SSR serverless-lift construct, did u have to write an
adapter to translate between Lambda request/response and Nuxt's SSR
request/response?
Frank
…--
<https://seed.run/>
Founder at SST <https://sst.dev>
SST <https://github.com/serverless-stack/serverless-stack> - OS framework
for building serverless apps
SEED <https://seed.run/> - Deploy, manage, and monitor serverless apps
On Mon, Jan 9, 2023 at 10:30 PM Jamie Owen ***@***.***> wrote:
Hi,
Apologies for requesting features via a Github Issue!
However i was wondering what plans ( if any ) there were for supporting a
Vue/ Nuxt 3 <https://nuxt.com/> SSR construct. Nuxt 3 uses the Nitro
engine <https://nitro.unjs.io/> to generate lambda code ( in .mjs format
)?
Or another alternative, do you have any plans for creating a generic SSR
Site construct that could be extended?
I have used the generic SSR serverless-lift construct
<https://github.com/getlift/lift/blob/master/docs/server-side-website.md>
with Nuxt 3 so far.
Cheers,
Jamie
—
Reply to this email directly, view it on GitHub
<#2314>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAUMO5527MPXJ2AFPWCD33WRTJVXANCNFSM6AAAAAATWE6U4E>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hey Frank, No not that i'm aware of. Essentially - Nuxt 3 / Nitro generates the Lambda handler from the It generates output folders Then configured the Serverless Lift plugin minimally with the following in the
Then the function handler looked like :
I haven't seen any errors so far. But early days :) |
Hey @jamieowen, quick update. SST now has an If you'd like to give it a go, u can try using Let me know if there's anything I can help w/. |
For anyone trying this I had success with the methods Frank and Jamie have mentioned.
I managed to get it working in this test repo . Caveat is lambda@edge support is waiting on this pr from the nuxt unjs team. Edit: |
Hi @jdevdevdev, thanks for working on this 🙏🏽 As you mention, there's 2 nitro PR open for lambda-edge support. Just to confirm, for SST support, you need an aws-lambda-edge without the cdk, correct ? |
@Hebilicious Correct. In my test repo deployment was handled by sst. Thanks for looking into it! |
I'm hoping this can be official supported at sometime because at viteconf Solidjs announced they were going to leverage nitrojs, the webserver that powers nuxt too. |
Hey @jdevdevdev! Is your test repo still working for you? |
I made a simple PoC for a simple NuxtSite with no edge support but handling IPX (for @nuxt/image, i.e., image compression). Here's the gist: https://gist.github.com/EnzoAlbornoz/b7a72f4651d404e756e18f8ca9fdde97 |
Thanks @EnzoAlbornoz ! I'll give it a try in a few days... |
@jdevdevdev just to let you know I did start a PR based mostly on your existing work unjs/nitro#1557 |
@EnzoAlbornoz hmm.. I couldn't get it working. The amplify gen 2 stuff looks promising though. It worked right away |
Sorry, I keep getting this when I'm trying to deploy
Any idea how to debug this? I'm trying to search all the places but maybe it's not correct direction... |
@8bu I keep getting this too! did you manage to solve it? |
Hi,
Apologies for requesting features via a Github Issue!
However i was wondering what plans ( if any ) there were for supporting a Vue/ Nuxt 3 SSR construct. Nuxt 3 uses the Nitro engine to generate lambda code ( in .mjs format )?
Or another alternative, do you have any plans for creating a generic SSR Site construct that could be extended?
I have used the generic SSR serverless-lift construct with Nuxt 3 so far.
Cheers,
Jamie
The text was updated successfully, but these errors were encountered: