Respect configured assetsDir for all assets #13173
Closed
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.
Since upgrading to the latest stable version of react-router we saw some output assets no longer being in
build/client/lite
, what we have configured invite.config.ts
, but instead inbuild/client/assets
, for exampleMultiStoreBoundary
of the ones shown below.Due to reasons all client assets must be in a folder called
lite
in our setup or they won't be accessible, so upgrading react-router brought down our app, in the condition that one entered it on a route that needed the files that were suddenly inassets
(additional to only happening in prod due to complicated reverse proxy setup but not dev when testing).This fixes the issue, by changing the hardcoded
assets
folder in thereact-router
vite plugin to instead respect thebuild.assetDir
from the users'vite.config.ts
file.