Steven ab9bada7b7 chore(export)!: remove next export in favor of output: export in next.config.js (#57085) ... BREAKING CHANGE Since `next export` has been printing a deprecation warning since https://github.com/vercel/next.js/pull/47376, its safe to remove in semver-major. The upgrade path is to simply add `output: 'export'` in `next.config.js` - everything will continue to work the same. This config greatly improves the `next dev` experience today. And in the future, it will improve performance of `next build` because we no longer need to do two passes (build then export).		2023-10-23 18:03:58 +00:00
..
pages	Error on query values in exportPathMap for auto export page (#9908)	2020-01-16 21:39:00 -05:00
test	chore(export)!: remove next export in favor of output: export in next.config.js (#57085)	2023-10-23 18:03:58 +00:00
next.config.js	chore(export)!: remove next export in favor of output: export in next.config.js (#57085)	2023-10-23 18:03:58 +00:00