-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
question: why did you change from unpkg to jsdelivr? #12
Comments
Hi @jthegedus. I made the switch after an unpkg bug broke redirect URLs (see mjackson/unpkg#156). Bugs happen, but this particular one took a long time to fix and was very hard to verify that the fix worked for everyone. As I mentioned in the linked issue:
The only hiccup I've experienced is that jsDelivr content is cached longer on both the server and the client, so getting the latest version immediately after release requires extra fiddling or patience. I mentioned this in a jsDelivr issue (jsdelivr/jsdelivr#18124) to which I received this helpful response from @MartinKolarik:
Makes sense, so I now do the following:
Seems to be working well so far. 😄 |
Very useful information. Thanks again for taking the time to formulate such a useful answer 😄 It'd probably be useful to have a comparison in Docsify. |
You bet. Happy to help. FWIW, I've filed an issue (docsifyjs/docsify#756) suggesting the maintainers consider making the same switch. It's easy enough for folks to choose jsDelivr over unpkg on their own if they are aware of it, but I suspect many docsify users blindly copy-paste the links provided in the docs. |
Your are 100% correct. I'm aware of unpkg, but was not aware of the differences between CDNs so blindly used unpkg. I think recommending unpkg during development and jsdelivr for prod stability is the way to go. |
Just curious
The text was updated successfully, but these errors were encountered: