Back to Signal Feed
CodeTracked since May 18, 2026

Bundle plugin runtime deps so marketplace installs can start correctly

This PR fixes a packaging regression by ensuring `plugin/` runtime dependencies are actually shipped in the marketplace bundle. It does two related steps: runs `npm install --production` when building the plugin package, and includes `plugin/node_modules` in `package.json` `files` so required modules (for example zod and parser/runtime deps) are present after install.

claude-memplugin/node_modulesscripts/build-hooks.jspackage.json

What Happened

  • This PR fixes a packaging regression by ensuring `plugin/` runtime dependencies are actually shipped in the marketplace bundle. It does two related steps: runs `npm install --production` when building the plugin package, and includes `plugin/node_modules` in `package.json` `files` so required modules (for example zod and parser/runtime deps) are present after install.
  • This PR fixes a packaging regression by ensuring `plugin/` runtime dependencies are actually shipped in the marketplace bundle. It does two related steps: runs `npm install --production` when building the plugin package, and includes `plugin/node_modules` in `package.json` `files` so required modules (for example zod and parser/runtime deps) are present after install.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduces an explicit production dependency install step in the plugin build flow and publishes `plugin/node_modules` with the extension package, so installed users receive all required runtime packages instead of a dependency-missing bundle.

Why Track This

Why It Matters

Users installing claude-mem from the marketplace are less likely to lose entire sessions silently because prompt-processing workers can start with the required runtime modules available instead of missing-dependency crashes. After this change, a startup failure path that previously left sessions un-summarized should stop happening, which removes a failure mode that could hide across platforms where local hook errors are not surfaced. Continue monitoring whether dependency updates outside this repo can reintroduce a gap between lockfile state and bundled modules, and watch installation size/upgrade behavior to ensure the bundle remains stable as dependencies change.

Impact

Users installing claude-mem from the marketplace are less likely to lose entire sessions silently because prompt-processing workers can start with the required runtime modules available instead of missing-dependency crashes. After this change, a startup failure path that previously left sessions un-summarized should stop happening, which removes a failure mode that could hide across platforms where local hook errors are not surfaced. Continue monitoring whether dependency updates outside this repo can reintroduce a gap between lockfile state and bundled modules, and watch installation size/upgrade behavior to ensure the bundle remains stable as dependencies change.

What To Watch Next

  • Watch whether claude-mem becomes a repeated pattern.
  • Track follow-up changes around AI IDE.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: silent_summary_loss_from_missing_runtime_modules, plugin_bundle_drift_after_dependency_updates.
Open Topic TimelineOpen Technical EventOpen Original Sourcesilent_summary_loss_from_missing_runtime_modules / plugin_bundle_drift_after_dependency_updates / marketplace_package_size_growth / lockfile_and_bundled_modules_skew

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

thedotmack/claude-mem PR #2531: fix(packaging): bundle plugin/node_modules so marketplace install ships runtime deps (closes #2407)

When the worker starts without bundled runtime deps, Claude-mem records prompts but cannot summarize them, producing silent data loss.