Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Page suggests deno add command that fails #760

Open
leighmcculloch opened this issue Oct 16, 2024 · 0 comments
Open

Page suggests deno add command that fails #760

leighmcculloch opened this issue Oct 16, 2024 · 0 comments

Comments

@leighmcculloch
Copy link

leighmcculloch commented Oct 16, 2024

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.

Screenshot 2024-10-16 at 3 37 11 PM

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs Triage
Development

No branches or pull requests

1 participant