Add explicit version to JavaScript package to bust importmap CDN cache #54
Conversation
This file contains 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
hopsoft
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The cache busting mechanic employed by jspm.io is based on hashing the contents of the package's
mainentrypoint. That strategy works great for normal JavaScript libraries, but many of my libraries are "joint" libraries having both a Ruby library and companion JavaScript library. I always release both libraries together (with the same version number) regardless if one of them didn't actually have changes. This makes it less confusing for folks keeping the libraries in sync for their applications.TLDR; jspm.io does not invalidate its cache for the JavaScript package and will continue to ship the last version of the library that included changes regardless of the current library version.