Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Adding a new package causes "pnpm install" to fail [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fresh fork and trying to add a new package to the project which triggers a dependency scan. This fails with [ERR_PNPM_EXOTIC_SUBDEP] Exotic dependency "libsignal" (resolved via git-repository) is not allowed in subdependencies when blockExoticSubdeps is enabled

Claude's analysis:

I found the root cause. Let me explain what's happening before suggesting a fix.

What's happening:

Your new packages/recall-bench-openclaw package itself doesn't depend on baileys — but adding any new workspace package triggers pnpm's runDepsStatusCheck (visible in the stack trace), which forces pnpm install to re-resolve and re-validate the whole graph.

The pre-existing extensions/whatsapp/package.json:11 pulls in [email protected], and baileys's own package.json declares its libsignal dependency as an aliased git/tarball spec (@whiskeysockets/libsignal-node from a codeload.github.com tarball — visible in pnpm-lock.yaml:11493). pnpm 11 ships with blockExoticSubdeps enabled by default, which refuses to install git/tarball deps that come in transitively rather than from your own package.json.

So the workspace has always had this exotic subdep — it just wasn't re-validated until now because pnpm install had no reason to re-resolve.

Error Message

  1. Run pnpm build to trigger the pnpm install error.

Root Cause

I found the root cause. Let me explain what's happening before suggesting a fix.

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Fresh fork and trying to add a new package to the project which triggers a dependency scan. This fails with [ERR_PNPM_EXOTIC_SUBDEP] Exotic dependency "libsignal" (resolved via git-repository) is not allowed in subdependencies when blockExoticSubdeps is enabled

Claude's analysis:

I found the root cause. Let me explain what's happening before suggesting a fix.

What's happening:

Your new packages/recall-bench-openclaw package itself doesn't depend on baileys — but adding any new workspace package triggers pnpm's runDepsStatusCheck (visible in the stack trace), which forces pnpm install to re-resolve and re-validate the whole graph.

The pre-existing extensions/whatsapp/package.json:11 pulls in [email protected], and baileys's own package.json declares its libsignal dependency as an aliased git/tarball spec (@whiskeysockets/libsignal-node from a codeload.github.com tarball — visible in pnpm-lock.yaml:11493). pnpm 11 ships with blockExoticSubdeps enabled by default, which refuses to install git/tarball deps that come in transitively rather than from your own package.json.

So the workspace has always had this exotic subdep — it just wasn't re-validated until now because pnpm install had no reason to re-resolve.

Steps to reproduce

  1. Fork OpenClaw
  2. Run pnpm install, pnpm OpenClaw setup, and pnpm build from OpenClaw directory. Verify everything builds.
  3. Add a new package to the packages folder.
  4. Run pnpm build to trigger the pnpm install error.

Expected behavior

The project should build if I add a new package.

Actual behavior

It doesn't build after adding any new package to the packages folder.

OpenClaw version

latest

Operating system

Windows 11

Install method

No response

Model

none

Provider / routing chain

none

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The project should build if I add a new package.

#database connection#vector store#embedding generation#cache error#pipeline error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Adding a new package causes "pnpm install" to fail [1 pull requests]