Deprecated version being used in the rewrite about jsdelivr HOT 7 CLOSED

Hey, I looked into this briefly, and I can see the npm cli itself does seem to ignore the deprecated version, but I'm not actually sure why - I couldn't find any resource or reference in their code so far that would suggest this should actually be the case. As a short-term solution, I'd certainly suggest using a more restrictive range.

from jsdelivr.

Thanks for looking into this! Is any of the code you use for deriving versions open source, so I might be able to take a look and see if I can contribute a patch? I've started rolling out more restrictive, but it isn't going to cure all combinations unfortunately.

from jsdelivr.

This part is not OSS unfortunately but I've actually found the details of npm's implementation recently: https://github.com/npm/cli/blob/88ece8161021997cb5c22040b34d0dffff55fcf1/node_modules/npm-pick-manifest/lib/index.js#L174-L180

I think we'll be able to adjust our behavior to match npm's shortly.

from jsdelivr.

Awesome - many thanks!

from jsdelivr.

Fixed! https://cdn.jsdelivr.net/npm/[email protected]/+esm now loads the correct version.

from jsdelivr.

Amazing - thank you for implementing that change, and so quickly!

from jsdelivr.

Wow, this is fantastic! Thank you!

from jsdelivr.