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
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Bug
npx @deepseek-ai/dsh web(and--help/--version) prints nothing and exits 0. The CLI never starts.Affects Node.js v23.x (entire line), v22 < 22.18.0, and v24 < 24.2.0.
Environment
@deepseek-ai/dsh@0.1.5-rc.1/0.1.5-rc.2Published
package.jsonhas noenginesfield.Repro
Shebang is
#!/usr/bin/env node. Direct Bun invocation works:bun node_modules/@deepseek-ai/dsh/lib/bin.js -V # 0.1.5-rc.2Root cause
lib/bin.jsends with:On Node.js without
import.meta.mainthis isundefined, sorunCli()never runs.import.meta.mainv23 sits between 22 and 24 by version number but never received the feature.
engines: ">=22.18.0"would incorrectly match v23.x.Suggested fix
A. Declare engines that exclude v23:
{ "engines": { "node": ">=22.18.0 <23.0.0 || >=24.2.0" } }npm only hard-fails this with
engine-strict.B. Fallback entry guard (if older Node.js / v23 should still work):
C. If Bun is the only runtime, change the shebang to
#!/usr/bin/env bunand document it. That contradicts the currentnpx+#!/usr/bin/env nodepath.Silent
exit 0is the worst CLI failure mode.Workaround
Upgrade Node.js to >=22.18.0 excluding v23, or >=24.2.0. Or run with Bun:
All reactions