Commit bd7a85e2 authored by Aziz Khambati's avatar Aziz Khambati Committed by Joe Haddad

Upgrade Doc: Note to remove @types/next (#7830)

* [doc] Add Uninstall @types/next in Upgrading Doc

* Apply suggestions from code review
Co-Authored-By: 's avatarTim Neutkens <tim@timneutkens.nl>

* Update UPGRADING.md

* Update UPGRADING.md
parent 9c8d34d5
...@@ -8,6 +8,25 @@ Next.js will now ignore usage `@zeit/next-typescript` and warn you to remove it. ...@@ -8,6 +8,25 @@ 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`.
TypeScript Definitions are published with the `next` package, so you need to uninstall `@types/next` as they would conflict.
The following types are different:
> This list was created by the community to help you upgrade, if you find other differences please send a pull-request to this list to help other users.
From:
```tsx
import { NextContext } from "next";
import { NextAppContext } from "next/app";
import { NextDocumentContext } from "next/document";
```
to
```tsx
import { NextPageContext } from "next";
import { AppContext } from "next/app";
import { DocumentContext } from "next/document";
```
#### The `config` key is now a special export on a page #### 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 ...`). You may no longer export a custom variable named `config` from a page (i.e. `export { config }` / `export const config ...`).
......
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