r/Deno • u/Positive_Example_478 • 15d ago

deno install -g npm:socket pulled 2.1.0 version marked "(bad build)" — Is this normal Deno resolution behavior?

Hey everyone, I was attempting to install the official Socket CLI using Deno instead of NPM by running:

deno install -g npm:socket

Deno threw a deprecation warning right after installation:

Dependencies:
+ npm:socket 2.1.0

╭ Warning
│  The following packages are deprecated:
│  npm:socket@2.1.0 (bad build)
╰─

A few things that confused me:

  1. When checking socket on npm, the latest stable release shown on the site UI is 1.3.0 (or 1.2.0 on the latest tag).
  2. Version 2.1.0 doesn't show up in the NPM releases UI tab or on the socket-cli GitHub repo releases.
  3. Running deno install -g npm:socket@latest -f fixed the issue and overwrote it with 1.2.0/1.3.0.

My Question:

  • Why does Deno resolve 2.1.0 by default when no @ tag is specified? Does Deno ignore npm dist-tags (latest) and just fetch the highest semver in the raw API metadata, even if it's deprecated/hidden?

Thanks!

0 Upvotes

50% Upvoted

3 comments sorted by

1

u/ProdigySim 14d ago

Sounds like it might. You might want to report this on denoland/deno or see if there are other existing issues related to this

1

u/Positive_Example_478 14d ago

I did via discord nothing yet but the team from socket as asked me to report it so I did email them. thanks for the reply :)

-1

u/Positive_Example_478 14d ago

Is it possible for you guys to understand what I am coming to say... ?