-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
SSR + serverless infrastructure #11231
Comments
Will be available through "@quasar/app" v3.2.0. |
@Seanitzel Will you be around tomorrow (Tuesday) to help me with some tests before I release the new q/app version? Would like to be 110% sure everything will work as smooth as possible. Can we connect through Discord to speed things up? |
To be honest tomorrow is the worst day possible for that since i'm having a surgery 😅😂 But I still might be able to, i'll hit you up on discord when i'll be back And thanks for addressing this issue so quickly! |
Hope all goes well!! Don't worry about me. |
Problem
Currently there is no way to export the handler when building a V2 SSR app.
The only way to make it happen is to literally edit the generated index.js file.
Describe the solution you'd like
A way to define exactly what will be exported from the SSR app built.
Describe alternatives you've considered
From reading the docs i understand that the only thing we can do at the moment is the different options that exist in Quasar.conf. None of them offer that.
Additional context
There is more information here:
https://github.com/l1qu1d/quasar-v2-ssr-firebase
My goal was to deploy the app to firebase cloud functions, and it doesn't work with the way the build is created at the moment.
The text was updated successfully, but these errors were encountered: