postinstall references missing scripts/postinstall.mjs — not included in published tarball

[doobidoo]

Bug

package.json declares:

"postinstall": "node scripts/postinstall.mjs"

but scripts/ is not listed in the "files" whitelist, so scripts/postinstall.mjs is excluded from the published npm package. Every npm install of context-mode@1.0.75 (and earlier versions with this layout) fails with:

Error: Cannot find module '.../scripts/postinstall.mjs'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1475:15)
    ...
    code: 'MODULE_NOT_FOUND'

Verification

• The file exists upstream on main (HTTP 200 on raw.githubusercontent.com/mksglu/context-mode/main/scripts/postinstall.mjs)
• It is missing from the installed package at .../context-mode/1.0.18/scripts/ (directory does not exist)
• package.json "files" field contains ["build", "hooks", ...] — no scripts entry

Impact

• macOS / Linux: cosmetic — the script is essentially a no-op on these platforms (OpenClaw detection message + Windows-only junction fix), so the install still functions.
• Windows + nvm4w global install: functional regression — the nvm4w directory-junction fix in postinstall.mjs never runs, so the context-mode.cmd shim can fail to resolve the package module path when npm prefix and node prefix are on different paths.

Reproduction

npm install -g context-mode@1.0.75
# → npm error command sh -c node scripts/postinstall.mjs
# → Error: Cannot find module '.../scripts/postinstall.mjs'

Also reproducible via the built-in upgrader:

node cli.bundle.mjs upgrade
# → "Update failed — GitHub pull failed — Cannot find module scripts/postinstall.mjs"

Fix

Add "scripts" to the files array in package.json:

"files": [
  "build",
  "hooks",
  "scripts",
  ...
]

Alternatively, inline the postinstall logic into build/ output if keeping scripts/ out of the tarball is intentional.

Environment

• context-mode@1.0.75
• Node.js v25.8.0
• macOS 25.3.0 (darwin-arm64)
• Claude Code plugin cache install path

Related

• Not a duplicate of [potential Security Alert] postinstall script changed in context-mode@1.0.35 #157 (that was about the postinstall content changing — security review). This is about the file being missing from the tarball entirely.
• Not a duplicate of FTS5/better-sqlite3: native binding missing on macOS global npm install with ignore-scripts=true #204 / FTS5/better-sqlite3: native binding missing on macOS global npm install with ignore-scripts=true #206 (those were FTS5 / better-sqlite3 native binding issues triggered by ignore-scripts=true).

[mksglu]

Already fixed since v1.0.75

scripts/postinstall.mjs has been in the files array since commit 4c319eb (PR #156), which shipped in the 1.0.75 release:

"files": [
  "build", "hooks", "configs", "server.bundle.mjs", "cli.bundle.mjs",
  "skills", ".claude-plugin", ".openclaw-plugin", ".mcp.json",
  "openclaw.plugin.json", "start.mjs", "scripts/postinstall.mjs",
  "README.md", "LICENSE"
]

Verified across all branches:

• main: ✅ present
• next: ✅ present
• v1.0.75 tag (commit 08bd59e): ✅ present

If you're still hitting MODULE_NOT_FOUND, possible causes:

1. Stale npm cache — try npm cache clean --force && npm install -g context-mode
2. Plugin marketplace cache — the marketplace may have cached an older tarball. Try /plugin uninstall context-mode then /plugin install context-mode@context-mode
3. ignore-scripts=true in your .npmrc — this prevents postinstall from running entirely (different error, same symptom)

If the issue persists after clearing caches, please share the output of:

npm pack context-mode --dry-run 2>&1 | grep postinstall