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

Note the config key is reserved (#7840)

Browse source 
Closes https://github.com/zeit/next.js/issues/7834
This commit is contained in:
Joe Haddad 2019-07-09 13:03:37 -04:00 committed by GitHub
parent a137447151
commit c650dca307
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
UPGRADING.md
View file

@ -8,6 +8,13 @@ Next.js will now ignore usage `@zeit/next-typescript` and warn you to remove it.
Usage of [`fork-ts-checker-webpack-plugin`](https://github.com/Realytics/fork-ts-checker-webpack-plugin/issues) should also be removed from your `next.config.js`.
#### The `config` key is now a special export on a page
You may no longer export a custom variable named `config` from a page (i.e. `export { config }` / `export const config ...`).
This exported variable is now used to specify page-level Next.js configuration like Opt-in AMP and API Route features.
You must rename a non-Next.js-purposed `config` export to something different.
#### `next/dynamic` no longer renders "loading..." by default while loading
Dynamic components will not render anything by default while loading. You can still customize this behavior by setting the `loading` property: