Why does Deno resolve npm:socket to socket@2.1.0 (bad build)?
⚙️Deno CLI
I'm trying to install the official Socket CLI using Deno:
deno install -g npm:socket
Deno installed:
npm:socket@2.1.0
and then showed:
The following packages are deprecated:
npm:socket@2.1.0 (bad build)
This confused me because the current Socket CLI documentation says to install the
I also noticed that explicitly using:
deno install -g npm:socket@latest
resolves to the expected current release instead.
My questions:
1. Why is
2. Is this expected Deno npm resolution behavior?
3. What exactly causes Deno to label
4. Is 2.1.0 an intentionally published/deprecated package version, a prerelease artifact, or something else?
5. Is there any security implication from Deno resolving this version?
I'm specifically interested in understanding what happened rather than just working around it with
Environment:
- macOS
- Deno v2.9.7
- Command:
deno install -g npm:socket
Deno installed:
npm:socket@2.1.0
and then showed:
The following packages are deprecated:
npm:socket@2.1.0 (bad build)
This confused me because the current Socket CLI documentation says to install the
socketsocket package, and the Socket GitHub repository does not appear to list 2.1.0 as a normal release.I also noticed that explicitly using:
deno install -g npm:socket@latest
resolves to the expected current release instead.
My questions:
1. Why is
npm:socketnpm:socket resolving to 2.1.0 rather than the npm latestlatest dist-tag?2. Is this expected Deno npm resolution behavior?
3. What exactly causes Deno to label
socket@2.1.0socket@2.1.0 as "(bad build)"?4. Is 2.1.0 an intentionally published/deprecated package version, a prerelease artifact, or something else?
5. Is there any security implication from Deno resolving this version?
I'm specifically interested in understanding what happened rather than just working around it with
@latest@latest.Environment:
- macOS
- Deno v2.9.7
- Command:
deno install -g npm:socketdeno install -g npm:socket
