chore: read manifest from one module instead of threading it through the server runtime

[Nic-Polumeyv]

Server keeps the manifest in #manifest and passes it to respond, from where it travels through 16 parameter positions in runtime/server, down to has_prerendered_path and load_error_components. The same object is written to runtime/server/internal.js by set_manifest in the Server constructor, and $app/server's read, $app/paths's resolve and the read_implementation branch in fetch.js already read it from there, so fetch.js mixed the parameter and the module singleton in one function.

The parameter is gone and every reader imports manifest from internal.js, the same shape #16871 gave options. The Server constructor argument and its set_manifest call stay. In dev that call runs per request, so a request in flight during a manifest regeneration now sees the regenerated manifest, which read and resolve already did.

Closes #16519.

[pkg-svelte-dev]

Install the latest version of @sveltejs/kit from 61e9ecb:

pnpm add https://pkg.svelte.dev/@sveltejs/kit/c/61e9ecbbd184796a0ecd17d5b81fecc27bf26bac

Open in pkg.svelte.dev: https://pkg.svelte.dev/repos/kit/pr/16967

[changeset-bot]

⚠️ No Changeset found

Latest commit: 61e9ecb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[svelte-docs-bot]

Preview: https://svelte-dev-git-preview-kit-16967-svelte.vercel.app/