fix (next): updated getting started guide after v5 tests #4805
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tannerabread
reviewed
Nov 9, 2022
Co-authored-by: Bannon Tanner <bannon.n.tanner@gmail.com>
…orded the [id].js instructions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Fixes to the Next.JS documentation for Getting Started with Amplify after
No current usererrors occurred when following steps in guide. Everything works locally, however there is an issue with Hosting tied to vercel/next.js#41932 and the Frontend build failing for CI/CD. The error in the logs is the following:By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.