Hi @jospalmbier many thanks for fixing | Friends of the Crustacean 🦞🤝 | Page 1

thanks for reporting this one. the clankers seem to assess it as being an underlying openclaw issue, since fixed:

Being NPM bullshit, I'm inclined to think that but I'm not sure. Let's assess. 
16:00




Worked for 24s
Not guesswork; evidence says: not npm being npm.

Failure step in the issue: pnpm build:plugin-sdk:dts; upstream defines that as plain tsc -p tsconfig.plugin-sdk.dts.json, not install/prune/rebuild noise.
Our Nix wrapper runs that same upstream step directly in gateway-build.sh (line 86). No Nix-specific transform there.
Our build env also does not set NODE_OPTIONS at all in openclaw-gateway-common.nix (line 68). So we did not “cause” it with a bad heap flag either.
Upstream then landed f4704184 on 2026-04-08: build: narrow plugin SDK declaration build. Patch shrinks DTS inputs from src/**/*.ts + packages/memory-host-sdk/src to a much smaller plugin-sdk subset.
That is a direct fix for TS declaration-memory pressure. Very strong signal: root cause upstream TypeScript/build scope, not random npm flakiness.
Current nix-openclaw pin is later, 0512059d / v2026.4.9-era openclaw-source.nix (line 5), and CI is green again.
Verdict: primarily upstream/OpenClaw build issue; surfaced in nix-openclaw because we build from source on limited-memory machines. Secondary nix-openclaw concern only if we want extra robustness for low-RAM source builds.

does that match what you're seeing?

#Hi @jospalmbier many thanks for fixing