Clicking the files tab on a package changes URL pattern for links in package nav about jsr

[crowlKats]

This is intentional behaviour, as when errors show up in runtime, they will be structured like that, so they can be just clicked on

[donjo]

I'm not sure I understand entirely. Here's an example of where the way it currently works could cause a confusing experience for a user.

Imagine I'm a user and I hear about a new package called @std/archive so I go to https://jsr.io/@std/archive to read more about it. I start clicking around to understand it's features and I click on the docs tab, read some docs, click on the versions tab to see how recently it has been updated, and lastly go to the files tab to see what the code actually looks like. Now I'm all done and I want to link the package to my team so I go back to the overview tab where I started and copy/paste the URL. However, the URL in my address bar is no longer a URL that will always link to the latest version of the package (https://jsr.io/@std/archive) but it links to whatever the latest version was at the time I happened to click the files tab before copying the URL from my address bar (https://jsr.io/@std/[email protected]).

The more I've thought about this I don't think the solution is just making the overview tab always link to the latest version's overview but I think the whole package header should probably be re-thought a bit to make it more clear when you are viewing content relevant to a specific version vs some universal metadata about the package