Updating nextjs.yml for Next.js 14 Support #2204
Merged
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.
PR Description
Overview
https://nextjs.org/blog/next-14#other-changes
This pull request tackles a major alteration incorporated in Next.js 14— the deprecation of the
next export
command, now supplanted byoutput: 'export'
as delineated in the Next.js documentation. By amending our codebase in alignment with this new provision, we're ensuring seamless compatibility moving forward.Background
The advent of Next.js 14 has ushered in a paradigm shift towards a more coherent and intuitive configuration ethos. A testament to this is the modification in the export functionality configuration, transitioning from
next export
tooutput: 'export'
, showcasing the framework's evolutionary trajectory.We're thankful for your meticulous review and comprehension.