Update introduction.md (#41226)
Fixed link to phases lines in the documentation ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com>
This commit is contained in:
parent
5e25bd2141
commit
87026c893b
1 changed files with 1 additions and 1 deletions
|
@ -62,7 +62,7 @@ module.exports = async (phase, { defaultConfig }) => {
|
|||
}
|
||||
```
|
||||
|
||||
`phase` is the current context in which the configuration is loaded. You can see the [available phases](https://github.com/vercel/next.js/blob/canary/packages/next/shared/lib/constants.ts#L1-L5). Phases can be imported from `next/constants`:
|
||||
`phase` is the current context in which the configuration is loaded. You can see the [available phases](https://github.com/vercel/next.js/blob/5e6b008b561caf2710ab7be63320a3d549474a5b/packages/next/shared/lib/constants.ts#L19-L23). Phases can be imported from `next/constants`:
|
||||
|
||||
```js
|
||||
const { PHASE_DEVELOPMENT_SERVER } = require('next/constants')
|
||||
|
|
Loading…
Reference in a new issue