Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This simplifies the build output and makes it closer to your standard Vite output by making a couple of changes:
We now leave Vite manifests in their default location, e.g.
build/client/.vite/manifest.json
andbuild/server/.vite/manifest.json
instead ofbuild/.vite/client-manifest.json
andbuild/.vite/server-manifest.json
. Note that these Vite manifests are deleted unless consumers explicitly enable them viabuild: { manifest: true }
in their Vite config. This means that the build output is now much closer to what you'd expect from a typical Vite project.We no longer have a
manifest
option to write a React Router build manifest to disk underbuild/.react-router/manifest.json
. This option was originally added in Remix for Vercel so that they could enable it in their preset but then was superseded by the more powerfulbuildEnd
hook which has access to the build manifest in memory. Since the RRv7 migration is a major release, it's a good opportunity to streamline the plugin API and remove the unnecessarymanifest
option.