archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/test/production/export
History
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
..
components Refactor next export tests (#45227) 2023-02-02 16:22:54 +00:00
pages Refactor next export tests (#45227) 2023-02-02 16:22:54 +00:00
public/about Refactor next export tests (#45227) 2023-02-02 16:22:54 +00:00
static/data Refactor next export tests (#45227) 2023-02-02 16:22:54 +00:00
index.test.ts 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