Repository navigation
Version browser dependency paths to prevent stale module export failures - #15
Merged
Merged
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
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.
A visitor with cached0.4 vendor modules could load the new entry script but fail linking diagnoseError and other v1 exports. Version the complete dependency paths: browser-1.0.0.js and vendor/v1 directories, preserving internal relative imports and license notices. Update all current entry scripts and cache queries together.
Reproduced in the signed-in browser from the public root, fixed locally and verified six site tests plus all five value panels/negative paths in jsdom. Final public-browser verification follows merge and deployment.