Unverified Commit c650dca3 authored by Joe Haddad's avatar Joe Haddad Committed by GitHub

Note the `config` key is reserved (#7840)

Closes https://github.com/zeit/next.js/issues/7834
parent a1374471
...@@ -8,6 +8,13 @@ Next.js will now ignore usage `@zeit/next-typescript` and warn you to remove it. ...@@ -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`. 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 #### `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: Dynamic components will not render anything by default while loading. You can still customize this behavior by setting the `loading` property:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment