Open WorldCat: Fall back to archived build ID (and asyncify) #3097
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
Much faster than archive.org.
To fix horrible performance in Sublime, which apparently is not optimized for thousands of lint errors.
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.
We try Google's cached version of the homepage, then Archive.org's, which should both be relatively recent. Old build IDs should remain valid for a little while (that's why Next.js uses them AFAIK - it lets old cached versions of the static frontend continue fetching server-side data for a while after a backend update). This does run the risk of breaking translation if the build ID expires before the cache is updated, but that's better than translation always failing for people who get 403'd by Cloudflare.