You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a version isn't provided, it doesn't install latest like i'd expect it to, but says the module was not found.
➜ deno i npm:storybook-solidjs-vite
error: npm:storybook-solidjs-vite was not found.
➜ deno i npm:[email protected]
Add npm:[email protected]
➜ deno i npm:storybook-solidjs-vite@latest
Add npm:[email protected]
The text was updated successfully, but these errors were encountered:
According to the npm docs the npm install command will always default to the latest tag if no version or tag requirement is specified, see https://docs.npmjs.com/cli/v10/commands/npm-install#description . There apparently is an option to configure that in npm, but I've never heard of anyone changing that, so we can probably ignore that.
But npm also allows you to do npm install foo@* which is different from npm install foo (= npm install foo@latest).
I think this issue uncovers two different bugs in our npm installation logic:
Our semver version comparison seems to ignore pre-release version when matching with *
We don't default to adding @latest when no version or tag is specified for npm packages.
That means both of these commands fail at the moment:
…dd npm:pkg` (#25858)
Fixes#25813.
I initially tried doing this in `deno_semver`, where it's a cleaner
change, but that caused breakage in deno in places where we don't expect
a tag (see #25857).
This does not fix wildcard requirements failing to choose pre-release
versions. That's a little more involved and I'll do a separate PR.
deno 2.0.0-rc.4+0cb00a6
https://www.npmjs.com/package/storybook-solidjs-vite
If a version isn't provided, it doesn't install
latest
like i'd expect it to, but says the module was not found.The text was updated successfully, but these errors were encountered: