-
Notifications
You must be signed in to change notification settings - Fork 154
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
Improve setup steps on deploying Nuxt app to AWS Amplify on docs #1439
Comments
Hi, dear @idorenyinudoh thanks for sharing feedback. The In regards of zero configs, the I will relay your feedback to the amplify team 👍🏼 |
okay, thanks for the clarification and feedback! |
@idorenyinudoh - let me know if you were able to deploy to AWS Amplify and have any feedback or comments |
yeah i was able to but, to get a successful deployment, i had to edit the default config generated by amplify |
Affected page
https://nuxt.com/deploy/aws-amplify
Description
The documentation states that the integration of a Nuxt 3 app with AWS Amplify requires zero configuration. But that is not the case and I'll explain why.
The default build config that AWS Amplify generates is this:
However, Nuxt's build (and generate) command generates an
.output
directory that contains the app's contents ready to be served.Hence, the
baseDirectory
property in Amplify's build config will need to be updated to.output/public
. Hence, Nuxt's integration with AWS Amplify isn't zero config.Happy to open a PR.
P.S: Nitro's docs might be misleading as well.
The text was updated successfully, but these errors were encountered: