Linking to specific version of package returns 404

[dkazmer]

Linking the following URL from Bluesky yields 404 error and the weird transformed URL thereafter.
https://npmx.dev/package/obsidium/v/3.1
https://npmx.dev/package/[name]/v/[version]-isr

npmx has a lot of flaws and they've blocked me there because I dared to expose them (even constructively).
I'll probably go back to using regular npmjs.com

[mikouaji]

Looks like a ISR regression, npmx tries to cache very aggressively so its possible with working on it this issue was introduced. Thanks for reporting.

[danielroe]

the issue here is that 3.1 is not a valid version.

you can use https://npmx.dev/package/obsidium/v/^3.1

we should probably improve the error you get when you link to an invalid/incomplete version (or redirect to a valid one)

npmx has a lot of flaws and they've blocked me there because I dared to expose them (even constructively).

no idea what you're talking about but we very much welcome the reporting of bugs 🙂

[dkazmer]

@mikouaji thanks. Yeah, I noticed the aggressive caching. I have to open up dev tools and then refresh the browser to load the new data.

@danielroe

no idea what you're talking about

I'm sure you don't but nonetheless...
The error message could include a note about proper version URLs (with the little cap), or better yet, just cache the same way as npmjs.com

[danielroe]

this isn't related to caching

[danielroe]

you can see npm doesn't work either, because it is an invalid version:

https://www.npmjs.com/package/obsidium/v/3.1

[dkazmer]

Test links for comparison
https://www.npmjs.com/package/obsidium/v/3.1.0
https://npmx.dev/package/obsidium/v/3.1.0

[dkazmer]

@danielroe the first in above test works as expected, while the second doesn't..
Test w/ cap: https://npmx.dev/package/obsidium/v/^3.1
This one kinda works, but omits the README

[alex-key]

Some more details for reproduction:

• Go to https://npmx.dev/package/obsidium
• Click 3.1.0 (latest version)
• See URL is correct (https://npmx.dev/package/obsidium/v/3.1.0)
• Refresh the page
• Url is broken, page is broken

I will try to investigate. It should be some incorrect logic with redirection for the latest version (where "package/{name}" and "package/{name}/v/{latest}" should be the same)

[alex-key]

Daniel @danielroe , I think the problem is some issue with ISR on a Vercel side (@mikouaji mentioned).
I tried to reproduce locally, but cannot do it (I suppose ISR cannot be tested locally).
Also on npmx.dev this issues is reproducible quite randomly. But it's always related to reloading a package page with version in URL (/package/[name]/v/[version]). The package above (https://npmx.dev/package/obsidium/v/3.1.0) - is a very good example, where issue is reproducible 90% of the time.

I suppose ISR is still quite fresh feature and seems like noone have enough expertise on this except you.