Problem
From our source code and documentation, linking to a library's "latest" docs may fail after a while, because the version has changed, and possibly that link may not even exist anymore. So it's best practice to link to a specific version.
So for example, it's better to link to https://webpack.js.org/v5/concepts/#entry than to https://webpack.js.org/concepts/#entry or https://webpack.js.org/latest/concepts/#entry, etc.
The docs site however only has implicit "latest", and v4 is on a different subdomain.
The latest version is 5.x.x, and we can't link to it.
Solution
Please add the "latest" version as well, e.g. "5.72.1". If that would get burdensome to update each time, then just "5.x.x" or "5" or "v5" would be fine too.
Problem
From our source code and documentation, linking to a library's "latest" docs may fail after a while, because the version has changed, and possibly that link may not even exist anymore. So it's best practice to link to a specific version.
So for example, it's better to link to
https://webpack.js.org/v5/concepts/#entrythan tohttps://webpack.js.org/concepts/#entryorhttps://webpack.js.org/latest/concepts/#entry, etc.The docs site however only has implicit "latest", and v4 is on a different subdomain.
The latest version is 5.x.x, and we can't link to it.
Solution
Please add the "latest" version as well, e.g. "5.72.1". If that would get burdensome to update each time, then just "5.x.x" or "5" or "v5" would be fine too.