feat(next export): add warning if using getInitialProps (#37642 )

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`

![image](https://user-images.githubusercontent.com/3806031/173214117-f5159f3a-778c-4177-894d-78e7bb0c80e7.png)

## 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>

2022-06-13 02:34:23 +00:00

527 B

Raw Blame History

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

527 B Raw Blame History

getInitialProps Export Warning

Why This Warning Occurred

Possible Ways to Fix It

Useful Links

527 B

Raw Blame History