6108f10799
This PR builds on the work from @hattakdev (PR went stale: https://github.com/vercel/next.js/pull/14499) and adds a new `integration` test for the new warning. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Errors have helpful link attached, see `contributing.md`  ## To run locally 1. `pnpm build` 2. `pnpm testonly test/integration/export-getInitialProps-warn/test/index.test.js` Fixes #13946 ## Notes <details> <summary>Click to toggle see</summary> I know the `contributing.md` doc said to avoid adding new tests to `integration`. It also said new tests should be written in TypeScript. I wasn't sure where to put the tests for this so I went with `integration`. I also didn't see many other tests written in TS in this part of the codebase so I stuck with `.js`. </details> Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com>
15 lines
527 B
Markdown
15 lines
527 B
Markdown
# getInitialProps Export Warning
|
|
|
|
#### Why This Warning Occurred
|
|
|
|
You attempted to statically export your application via `next export`, however, one or more of your pages uses `getInitialProps`.
|
|
|
|
Next.js discourages you to use `getInitialProps` in this scenario.
|
|
|
|
#### Possible Ways to Fix It
|
|
|
|
Next.js has a proper SSG support, so usage of `next export` should always be paired with `getStaticProps`.
|
|
|
|
### Useful Links
|
|
|
|
- [`getStaticProps` Documentation](https://nextjs.org/docs/basic-features/data-fetching/get-static-props)
|