LukeParke/vercel
1
0
Fork 0
mirror of https://github.com/LukeHagar/vercel.git synced 2025-12-09 12:57:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

[docs] Replace references to @now/next in error docs (#9331)

Browse Source 
It's been long enough I think we can change these to refer to
`@vercel/next` instead.

x-ref: [slack
thread](https://vercel.slack.com/archives/C03DQ3QFV7C/p1674849801196389)
This commit is contained in:
JJ Kasper
2023-01-27 13:59:42 -08:00
committed by GitHub
parent 7110cb449b
commit 54aaab83aa
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
errors/now-next-legacy-mode.md
View File

@@ -1,8 +1,8 @@
# `@now/next` Legacy Mode # `@vercel/next` Legacy Mode
#### Why This Warning Occurred #### Why This Warning Occurred
`@now/next` has two modes: `legacy` and `serverless`. You will always want to use the `serverless` mode. `legacy` is to provide backwards compatibility with previous `@now/next` versions. `@vercel/next` has two modes: `legacy` and `serverless`. You will always want to use the `serverless` mode. `legacy` is to provide backwards compatibility with previous `@vercel/next` versions.
The differences: The differences:
@@ -63,7 +63,7 @@ module.exports = {
```js ```js
{ {
"version": 2, "version": 2,
"builds": [{ "src": "package.json", "use": "@now/next" }] "builds": [{ "src": "package.json", "use": "@vercel/next" }]
} }
``` ```

6
errors/now-next-no-serverless-pages-built.md
View File

@@ -1,4 +1,4 @@
# `@now/next` No Serverless Pages Built # `@vercel/next` No Serverless Pages Built
#### Why This Error Occurred #### Why This Error Occurred
@@ -33,13 +33,13 @@ module.exports = {
}; };
``` ```
4. Remove `distDir` from `next.config.js` as `@now/next` can't parse this file and expects your build output at `/.next` 4. Remove `distDir` from `next.config.js` as `@vercel/next` can't parse this file and expects your build output at `/.next`
5. Optionally make sure the `"src"` in `"builds"` points to your application `package.json` 5. Optionally make sure the `"src"` in `"builds"` points to your application `package.json`
```js ```js
{ {
"version": 2, "version": 2,
"builds": [{ "src": "package.json", "use": "@now/next" }] "builds": [{ "src": "package.json", "use": "@vercel/next" }]
} }
``` ```