Skip to content

Commit

Permalink
Change manifestPath to pagesManifestPath (#59657)
Browse files Browse the repository at this point in the history
## What?

Small clarification on the variable name.

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->


Closes NEXT-1882
  • Loading branch information
timneutkens authored Dec 15, 2023
1 parent d320556 commit 5d091ed
Showing 1 changed file with 8 additions and 4 deletions.
12 changes: 8 additions & 4 deletions packages/next/src/build/index.ts
Original file line number Diff line number Diff line change
Expand Up @@ -947,7 +947,11 @@ export default async function build(
const outputFileTracingRoot =
config.experimental.outputFileTracingRoot || dir

const manifestPath = path.join(distDir, SERVER_DIRECTORY, PAGES_MANIFEST)
const pagesManifestPath = path.join(
distDir,
SERVER_DIRECTORY,
PAGES_MANIFEST
)

const { incrementalCacheHandlerPath } = config.experimental

Expand Down Expand Up @@ -977,7 +981,7 @@ export default async function build(
relativeAppDir: path.relative(outputFileTracingRoot, dir),
files: [
ROUTES_MANIFEST,
path.relative(distDir, manifestPath),
path.relative(distDir, pagesManifestPath),
BUILD_MANIFEST,
PRERENDER_MANIFEST,
PRERENDER_MANIFEST.replace(/\.json$/, '.js'),
Expand Down Expand Up @@ -1203,7 +1207,7 @@ export default async function build(
const appDefaultConfigs = new Map<string, AppConfig>()
const pageInfos = new Map<string, PageInfo>()
const pagesManifest = JSON.parse(
await fs.readFile(manifestPath, 'utf8')
await fs.readFile(pagesManifestPath, 'utf8')
) as PagesManifest
const buildManifest = JSON.parse(
await fs.readFile(buildManifestPath, 'utf8')
Expand Down Expand Up @@ -2778,7 +2782,7 @@ export default async function build(
// remove temporary export folder
await fs.rm(exportOptions.outdir, { recursive: true, force: true })
await fs.writeFile(
manifestPath,
pagesManifestPath,
formatManifest(pagesManifest),
'utf8'
)
Expand Down

0 comments on commit 5d091ed

Please sign in to comment.