Install Fails on Old Node — DeepSeek Harness Guide
Symptom
Section titled “Symptom”Running the standard install/run command fails, or appears to hang, with a warning like this in the console:
npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException insteadReported for both npx @deepseek-ai/dsh web and plain npm install. (Discussion #897)
dsh’s package.json declares:
"engines": { "node": "^22.19.0 || >=24.0.0" }That’s 22.19.0 or later on the 22.x line, or 24.0.0 and up. No patch version of 23.x qualifies, since 23 is a dead non-LTS line. Outside that range, dependency resolution gets unpredictable and can pull in old transitive packages like node-domexception, which is where the warning above comes from. Installation covers why the floor sits where it does.
The version story doesn’t account for the whole thread. The top-voted answer in #897 says to upgrade Node, but other replies report the same warning on v22.23.1 and v24.14.1, both of which satisfy the documented floor. Nobody in the thread gets past the version guidance to a root cause. If you’re on a supported Node and still stuck, this may not be a version problem at all. Registry or network slowness with npx produces a similar-looking hang.
Solution
Section titled “Solution”- Check your Node version:
node -v. - If it’s outside
^22.19.0 || >=24.0.0(including anywhere in the 23.x line), upgrade to a supported version and retry. - If you’re on a supported version already, two workarounds were reported to help:
- Clone the repo and build from source instead of using
npx:Terminal window git clone https://github.com/deepseek-ai/deepseek-harness.gitcd deepseek-harnesspnpm installpnpm run buildpnpm dsh web - Install globally instead of via
npx:Terminal window npm install -g @deepseek-ai/dsh
- Clone the repo and build from source instead of using
Neither one is an official fix. They’re what worked for the people who reported back. If you try one, post the outcome in the Discussion.
Source
Section titled “Source”Related errors
Section titled “Related errors”- Windows sandbox crashes after clearing Temp — another environment-specific install/runtime issue.
- Thinking mode: 400 INVALID_REQUEST on tool calls — a runtime error once dsh is up and running.
- Back to Installation for the full install walkthrough.