Fix: include pathPrefix in resource check to prevent 404 React crash … #39367
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gatsbot
bot
added
the
status: triage needed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…(#32142)
Description
This PR updates the resource check login in
packages/gatsby/cache-dir/loader.jsto include thepathPrefixwhen resolving resources. Without this, sites configured with a custompathPrefixcould trigger 404 errors and React crashes during client-side navigation.Documentation
This change does not affect public APIs or require new documentation. It simply ensures correct path handling in existing resource resolution logic.
Tests
pathPrefixconfigured ingatsby-config.js.Related Issues
Fixes #32142