openclaw - 💡(How to fix) Fix Declare node-gyp for local native package builds [1 pull requests]

Problem

A fresh local install can fail when sharp falls back to building from source and cannot find a project-local node-gyp binary.

Observed while running pnpm docs:list from a checkout without installed dependencies. The docs command triggered dependency hydration, then sharp ran its install script and failed with:

node_modules/sharp install: sharp: Attempting to build from source via node-gyp
node_modules/sharp install: sharp: Found node-addon-api 8.7.0
node_modules/sharp install: sharp: Please add node-gyp to your dependencies
node_modules/sharp install: Failed
[ELIFECYCLE] Command failed with exit code 1.

Why this matters

OpenClaw does not directly invoke node-gyp, but native package postinstall scripts can. In this environment, sharp detected a source-build path and expected node-gyp to be available from the workspace dependency graph. Without declaring it, normal repo bootstrap commands can fail before any OpenClaw code runs.

Declaring node-gyp as a root dev dependency makes that native-build fallback reproducible and avoids relying on a globally installed node-gyp.

Proposed fix

Add node-gyp to the root devDependencies and update pnpm-lock.yaml.

Verification

With node-gyp declared locally:

• pnpm install completes
• pnpm docs:list completes
• pnpm exec node-gyp --version prints v12.3.0