This repository has been archived by the owner on Jun 1, 2023. It is now read-only.
Fix CORS (Cross-origin resource sharing) errors #1952
Merged
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.
WHY are these changes introduced?
Some assets don't load from the
LocalAssets
middleware because their path doesn't match or is not a static theme path. So, they load from the CDN, and cross-origin resource sharing errors happen.WHAT is this pull request doing?
Like the
CdnFonts
middleware, theCdnAssets
requests assets to serve them locally. But, it checks ifLocalAssets
are not handling the file.How to test your changes?
shopify theme init
to create a new themeshopify theme serve
Before this PR:
After this PR:
Click here to check a details about the 404 error
This error also happens in the preview store:
Post-release steps
None.
Update checklist