archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Correct info about export limitations (#7729)

Browse source 
* Correct info about export limitations

In `next export` `req` and `res` objects are present, but they are empty ( https://github.com/zeit/next.js/blob/master/packages/next/export/worker.js#L42-L43 ).

* Update README.md
This commit is contained in:
Jack Tomaszewski 2019-07-16 13:38:17 +02:00 committed by Tim Neutkens
parent 2c28e12220
commit 17773a6203
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
packages/next/README.md
View file

@ -2493,7 +2493,7 @@ now
With `next export`, we build a HTML version of your app. At export time we will run `getInitialProps` of your pages.
The `req` and `res` fields of the `context` object passed to `getInitialProps` are not available as there is no server running.
The `req` and `res` fields of the `context` object passed to `getInitialProps` are empty objects during export as there is no server running.
> **Note**: If your pages don't have `getInitialProps` you may not need `next export` at all, `next build` is already enough thanks to [automatic prerendering](#automatic-prerendering).