plugin install: TUI plugin fails with empty NpmInstallFailedError — resolver rejects a spec npm installs fine #50080

Activity

1. CENFARG commented on Oct 16, 2026

   

   CENFARG

   on Oct 16, 2026

   More actions

   Cross-platform + current-version data point confirming this (Windows 11, opencode 2.0.30, node 24.14.1):

   • Bare entry in cli.json fails identically: NpmInstallFailedError (cause: Error: unable to resolve dependency tree) at Npm.reify, reconciling on every start. [email protected] and @1.6.8 (exact) both install fine through OpenCode — so only the tag spec path fails, matching your 1.6.8 observation and extending it to the latest release.
   • Differential harness with opencode's own installer stack (@npmcli/[email protected], empty staging dir, reify({add: [spec]}, audit:false, ignoreScripts:true, binLinks:true, save:true) + @npmcli/[email protected] defaults): the tag spec succeeds standalone under both Node 24.14.1 and Bun 1.4.2. Same registry cache, same manifests — which supports your per-spec resolver/cache state hypothesis inside OpenCode's bundled client.
   • Reproduced fully isolated via XDG_CACHE_HOME/XDG_CONFIG_HOME sandbox (production config verified unchanged by hash).
   • Workaround we shipped to users: pin the exact version in config.

   Happy to test any candidate fix on Windows.
2. diegoolherry commented on Oct 20, 2026

   

   diegoolherry

   on Oct 20, 2026

   More actions

   Reproduces on Windows with opencode 2.1.1, so this is still present after the 2.0.x reports.

   Environment:

   • opencode v2.1.1, channel latest, installed via npm (@opencode/cli)
   • Windows 10.0.19045 (win32 x64), Node v24.11.1, npm 11.19.0
   • Terminal: WezTerm (TERM_PROGRAM=WezTerm); shell: cmd.exe / PowerShell

   Observed:

   1. opencode plugin add opencode-sdd-engram-manage -> NpmInstallFailedError: with an empty message, exit 1. opencode plugin update opencode-sdd-engram-manage prints No plugin updates available followed by the same empty error.
   2. Server startup logs the same empty NpmInstallFailedError on both reconciliation passes (durationMs=2865, then 285) for target=opencode-sdd-engram-manage install=true role=cli.
   3. In an empty directory, {"dependencies":{"opencode-sdd-engram-manage":"1.7.0"}} + npm install succeeds (131 packages, ~22s); only EBADENGINE warnings for @opentui/[email protected] (it requires node >=26.4.0, host has 24.11.1).
   4. ~/.cache/opencode/npm/opencode-sdd-engram-manage@latest stays empty - no <epoch> staging directory is ever created - while the healthy opencode-subagent-statusline@latest/<epoch>/ is populated normally with package.json and node_modules/.
   5. Moving the stale ~/.cache/opencode/packages/opencode-sdd-engram-manage@latest aside does not help; the next attempt fails again with the same empty error.
   6. opencode plugin add [email protected] succeeds, and opencode plugin check then exits 0 with both TUI plugins reported (current).

   This confirms the per-spec resolver/cache-state diagnosis: 1.7.0 fails and 1.6.8 installs through the same code path, and the pinned-1.6.8 workaround also works on Windows.
3. rudy500 commented on Oct 22, 2026

   

   rudy500

   on Oct 22, 2026

   More actions

   Still reproduces on v2.1.2 (Windows) — this issue is the closest match, adding occurrence evidence.

   • opencode plugin add opencode-sdd-engram-manage (bare name → tag spec, dist-tag latest = 1.7.0) fails deterministically, exit 1, across multiple runs:

     NpmInstallFailedError
       [cause]: Error: unable to resolve dependency tree
         at Npm.reify
     

     and startup reconciliation logs the same WARN with error=NpmInstallFailedError target=opencode-sdd-engram-manage.
   • opencode plugin add [email protected] succeeds through the identical code path (exit 0, cache generation created). The ~/.cache/opencode/npm/opencode-sdd-engram-manage@latest workspace stays empty — reproduces the empty-workspace observation above.
   • Manual npm install [email protected] with system npm succeeds in ~11s, so the tree is resolvable; same conclusion as the standalone arborist harness in the duplicate closed as plugin add with a tag spec (bare name / @latest) fails with ERESOLVE for some packages; exact version installs fine #56091.
   • Workaround confirmed for a clean startup: pin "[email protected]" in cli.json and drop the bare entry — with the bare entry kept, every TUI start retries and logs the failure again.

   Environment: opencode v2.1.2, Windows 11 (win32 x64), node v24.18.0, npm 12.2.0, registry https://registry.npmjs.org/, empty user .npmrc.
4. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Thanks for the detailed report. I can reproduce this on v2.0.10, and it still happens on the latest dev (62ae125).

   It only affects the bare spec:

   • opencode plugin add opencode-sdd-engram-manage fails with an empty NpmInstallFailedError: and [cause]: Error: unable to resolve dependency tree.
   • opencode plugin add opencode-sdd-engram-manage@latest, @1.7.0 and @^1.7.0 all install fine.

   It looks like the cause is not per-package cache state but how a bare name is resolved. The bun runtime OpenCode runs on reports its Node version as v26.x. A bare name is resolved as the range *, and npm's version picker then skips versions whose engines.node (>=24 <25, which 1.3.0 and later declare) rules out v26. It falls back to 1.2.0, which declares no node engine but has old peers (@opentui/core ^0.1.100). Those peers conflict with the current @opentui/core, and that's the ERESOLVE. A tag or exact version skips that path, which is why pinning 1.6.8 worked for you. In the meantime, an @latest entry instead of the bare name should also work.

   The empty error message is real too: the error class has no message of its own, so the CLI shows the cause only under [cause]. I didn't test the startup-log path myself, but that would explain why your reconciliation logs show only the error name.

   The script below reproduces it.

   Reproduction script (repro.sh)

   #!/usr/bin/env bash
   # Repro for #50080: bare plugin spec fails, @latest / exact version succeed.
   # Requires: opencode (bun add -g @opencode/[email protected]) and npm on PATH.
   set -u
   OC=${OC:-opencode}
   export HOME=$(mktemp -d)   # isolated config + ~/.cache/opencode/npm
   cd "$(mktemp -d)"
   $OC --version
   bun -e 'console.log("bun-reported process.version:", process.version)' 2>/dev/null || true
   echo "engines.node of 1.7.0: $(npm view [email protected] engines.node)"
   for spec in opencode-sdd-engram-manage opencode-sdd-engram-manage@latest [email protected]; do
     echo "== opencode plugin add $spec"
     $OC plugin add "$spec" 2>&1 | grep -E "NpmInstallFailedError|cause|installed"
   done

   Run it: bash repro.sh
5. opencodejr

   added

   reproduced

   on Oct 28, 2026