Skip to content
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

Update hosting_nextjs.yml #38

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

damianzm-aws
Copy link

Next.js needs Node 18.18 or later
https://nextjs.org/docs/getting-started/installation

next export has been removed in favor of 'output: export' in next.config.js.
Learn more: https://nextjs.org/docs/app/building-your-application/deploying/static-exports

Issue number:
#7

Summary

Currently the latest Next.js starter application from npx create-next-app@latest fails build process with CodeBuild because of version incompatibilities, which these build configuration changes resolve at present time.

Changes

Please provide a summary of what's being changed

Node version is set to 18.18 which is required per https://nextjs.org/docs/getting-started/installation

npx next export has been removed in favor of 'output: export' in next.config.js per https://nextjs.org/docs/app/building-your-application/deploying/static-exports

User experience

Please share what the user experience looks like before and after this change

Currently deploying using Wizard for Next.js repository fails at cloudfront-hosting-toolkit deploy

With these changes the Wizard can successfully build and deploy at Next.js repository

Users should understand the limitations of fully static Next.js hosting per https://nextjs.org/docs/app/building-your-application/deploying/static-exports and further updates to documentation should be considered to make this clear.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

  • [x ] I have performed a self-review of this change
  • [x ] Changes have been tested
  • Changes are documented
Is this a breaking change?

No

RFC issue number:

Checklist:

  • Migration process documented
  • Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Next.js needs Node 18.18 or later
https://nextjs.org/docs/getting-started/installation

`next export` has been removed in favor of 'output: export' in next.config.js.
Learn more: https://nextjs.org/docs/app/building-your-application/deploying/static-exports
@michaellisitsa
Copy link

Can +1 I had to make the same 2 changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants