25efdfad36
## Background In the early days, `next export` was created when Next.js was SSR-only in order to statically export your pages for self hosting where no server was available. However, around the time `getStaticProps()` and `getStaticPaths()` were introduced, Next.js began [automatically generating static pages](https://nextjs.org/docs/advanced-features/automatic-static-optimization) (SSG first and SSR opt-in) during `next build`. This meant there were very few reasons to use `next export` and it started to become a stale feature. ## Problem We Need To Solve Users targeting `next export` currently have a really bad experience. They start a new project and use all the features Next.js has to offer because they all features work with `next dev`. Then when development is finished and it comes time to deploy, running `next build && next export` will fail with errors for [unsupported features](https://nextjs.org/docs/advanced-features/static-html-export#unsupported-features). ## Solution This PR introduces a new configuration option, `output: 'export'`, to indicate that the user intends to run `next export`. With this change, Next.js can fail fast during `next dev` if any [unsupported features](https://nextjs.org/docs/advanced-features/static-html-export#unsupported-features) are used, thereby improving developer experience with instant feedback. ```js /** * @type {import('next').NextConfig} */ const nextConfig = { output: 'export', } module.exports = nextConfig ```
4 lines
60 B
JavaScript
4 lines
60 B
JavaScript
// prettier-ignore
|
|
module.exports = {
|
|
output: 'export',
|
|
}
|