![[]](https://github.githubassets.com/assets/platform-4ce65ae0bf273ce2.png){kind=link}
![[]](https://github.githubassets.com/assets/platform-dark-ac89fbf373737ed3.png){kind=link}
![[]](https://github.githubassets.com/assets/copilot-e2b89335a66dba00.png){kind=link}
![[]](https://github.githubassets.com/assets/copilot-dark-2b28403b6080e898.png){kind=link}
![[]](https://github.githubassets.com/assets/changelog-fd687bff072883b0.png){kind=link}
![[]](https://github.githubassets.com/assets/changelog-dark-b1c25ae971bd641b.png){kind=link}
![[]](https://github.githubassets.com/assets/universe-a98cd54821b27569.png){kind=link}
Repository navigation
Specify major version number in URLs#780
Description
The HTML rendered by docsify-cli and listed in the Manual Installation section of the official docs results in the very latest version of docsify being loaded by default. This is not only bad practice generally speaking, but it also means that breaking changes introduced in a new major release could break a lot of live docsify sites.
The suggested fix is to specify a major version number in all docsify URLs:
<link rel="stylesheet" href="//unpkg.com/docsify@4/themes/vue.css">
<script src="//unpkg.com/docsify@4/lib/docsify.min.js"></script>This means that when a new major version is released, site admins will need to manually update the URLs with the new major version number (e.g. @5). The benefit of this approach is that breaking changes in the new release will not affect existing docsify sites since they are loading the previous version.
If URLs are being updated, it's also worth considering the following:
- Use CDN redirect URLs instead of specifying a path for the main lib file
- Specify the URL scheme to avoid unnecessary redirects (i.e use
https://instead of//) - Switch to jsDelivr (Consider jsDelivr over unpkg for CDN#756) for better CDN performance
<script src="https://cdn.jsdelivr.net/npm/docsify@4/themes/vue.css"></script>
<script src="https://cdn.jsdelivr.net/npm/docsify@4"></script>Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
Issue actions
[]Open in GitHub Copilot app
![[]](https://github.githubassets.com/assets/github-copilot-app-light-15ad5534265eeacd.svg){kind=link}
Activity
timaschew commented on Feb 25, 2019
So this issue should be then migrated (or at least linked) to the CLI project, right?
jhildenbiddle commented on Feb 28, 2019
It's a valid issue for this repo since the Manual Installation section of the docs needs to be updated, but yes--work will also need to be done in the CLI repo.
I've made a similar issue in the CLI repo.
trusktr commented on Jun 21, 2020
Shouldn't this be in the 4.x project board?
jhildenbiddle commented on Jun 21, 2020
Yep. Done.
fix: Updated docs with instructions for installing specific version (f
Merge branch 'develop' into docsify-class