df378d33ef
Some checks failed
CI / go (push) Waiting to run
CI / docker (push) Waiting to run
CI / lint-go (push) Waiting to run
CI / lint-docs (push) Waiting to run
CI / check-paperclip (push) Waiting to run
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Resolved conflicts by taking GitHub versions for: - .dockerignore, .gitignore, Dockerfile, README.md, docker-compose.yml Kept deploy.sh updated to: - Pull from GitHub (primary source) - Push to Gitea (push-mirror) - Build from site/ directory (GitHub structure) Co-Authored-By: Paperclip <noreply@paperclip.ing>
2.1 KiB
2.1 KiB
| title | description | related | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Upgrading | Learn how to upgrade your Next.js application to the latest version or canary. |
|
Latest version
To update to the latest version of Next.js, you can use the upgrade command:
pnpm next upgrade
npx next upgrade
yarn next upgrade
bunx next upgrade
Versions before Next.js 16.1.0 do not support the upgrade command and need to use a separate package instead:
npx @next/codemod@canary upgrade latest
If you prefer to upgrade manually, install the latest Next.js and React versions:
pnpm i next@latest react@latest react-dom@latest eslint-config-next@latest
npm i next@latest react@latest react-dom@latest eslint-config-next@latest
yarn add next@latest react@latest react-dom@latest eslint-config-next@latest
bun add next@latest react@latest react-dom@latest eslint-config-next@latest
Canary version
To update to the latest canary, make sure you're on the latest version of Next.js and everything is working as expected. Then, run the following command:
pnpm add next@canary
npm i next@canary
yarn add next@canary
bun add next@canary
Features available in canary
The following features are currently available in canary:
Authentication: