-
Notifications
You must be signed in to change notification settings - Fork 27.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
Update next export
documentation.
#31465
Conversation
Co-authored-by: Rich Haines <hello@richardhaines.dev> Co-authored-by: Matthew Sweeney <mail@mcs.dev>
Sorry for the slow update, this is now ready for review again 😄 |
@leerob @MaedahBatool looks like we have soem cross over with 2 PRs here: #31906 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left one comment regarding a more descriptive heading. Other than that LGTM. There is another PR open that is also working on this section: #31906. Might be good to reach out to @MaedahBatool
@molebox Fixed! Ready to ship 😄 |
Building off #31465 for `next export` docs. - Clearly explains the standard output from `next build` - Move Dockerfile snippet to example, instead of embedded directly - Clarify both Vercel and `next start` use the Build API output spec - Less emphasis on recommending Vercel (more neutrality) - Mention Middleware & Edge Functions when discussing Vercel - Add "Going to Production" link at the bottom for related reading
This more clearly lists what features are supported and not supported by
next export
.