You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linked dependencies, as in <script src="//cdn.jsdelivr.net/npm/docsify/lib/plugins/search.min.js"></script> don't have a version in their URL, meaning they will always point to the latest version. (Side note: why do these dependencies start with // instead of https://?). This has two risks:
A new version might break the guide (through a bug or a changed API)
If we pin those dependencies, is there some way to automate updating them so we don't end up with very outdated dependencies one or two years from now?
I was thinking of automatically creating a pull request to update the version, so we can review if anything is broken. Would something like that be possible without too much effort?
Linked dependencies, as in
<script src="//cdn.jsdelivr.net/npm/docsify/lib/plugins/search.min.js"></script>
don't have a version in their URL, meaning they will always point to the latest version. (Side note: why do these dependencies start with//
instead ofhttps://
?). This has two risks:If you take off the last part of the path of these dependcies (e.g. https://cdn.jsdelivr.net/npm/docsify/lib/plugins/), you can navigate through the versions.
Furthermore, we should use integrity checks to ensure that the loaded code has not been altered with.
The text was updated successfully, but these errors were encountered: