Page suggests deno add command that fails

[leighmcculloch]

Loving the new registery 👏🏻

It appears that the jsr website provides an instruction to use deno add <package> to install, even when viewing specific versions of a package.

I can see how that would make sense a lot of the time, however when viewing a release candidate version of a package that has not yet created a stable release, that command will always error.

For example, when I visit the page for @cliffy/command the command on the right says to run deno add @cliffy/command.

When I run that command, I see an error that makes it sound like the package is missing all together.

$ deno add @cliffy/command
error: @cliffy/command was not found in either jsr or npm.

I understand the add command when not given a version is looking for the latest stable release and not finding one.

The error message could be more helpful. It could say in this case that @cliffy/command was found but no stable version was found, and to add an unstable version the version must be specified.

The jsr website could also include the version in the command to copy-paste so that folks get it right first time.

[lucacasonato]

Where are you seeing this? The right hand sidebar says deno add jsr:@cliffy/command (note the jsr:).

[leighmcculloch]

Adding the jsr: prefix makes no difference in this instance. If you note with the error message above it searched both jsr and npm.

Here is the command with the jsr prefix displaying the same / similar error:

$ deno add jsr:@cliffy/command
error: jsr:@cliffy/command was not found.

And here it is working when a version is specified.

$ deno add jsr:@cliffy/[email protected]
Add jsr:@cliffy/[email protected]

A version is required because there is no stable version of @cliffy/command published. All the versions published are pre-release versions, and deno add is only looking for stable versions when no version is specified.