Back to Signal Feed
CodeTracked since May 18, 2026

Bundle claude-mem plugin runtime dependencies in release artifacts

The PR fixes packaging by running `npm install --production` during `scripts/build-hooks.js` and adding `plugin/node_modules` to the package `files`, so runtime modules such as `zod`, `shell-quote`, and `tree-sitter-*` are shipped with the marketplace bundle instead of being omitted at publish time.

claude-memscripts/build-hooks.jsplugin/package.jsonplugin/node_modules

What Happened

  • The PR fixes packaging by running `npm install --production` during `scripts/build-hooks.js` and adding `plugin/node_modules` to the package `files`, so runtime modules such as `zod`, `shell-quote`, and `tree-sitter-*` are shipped with the marketplace bundle instead of being omitted at publish time.
  • The PR fixes packaging by running `npm install --production` during `scripts/build-hooks.js` and adding `plugin/node_modules` to the package `files`, so runtime modules such as `zod`, `shell-quote`, and `tree-sitter-*` are shipped with the marketplace bundle instead of being omitted at publish time.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Implemented a packaging change that materializes plugin runtime dependencies during build and includes them in the published payload, which directly addresses missing-dependency runtime failures in end-user installs.

Why Track This

Why It Matters

Users and operators on macOS/Windows are less likely to lose prompt sessions silently after upgrades, because the plugin package will now include the runtime modules needed for the worker to start and summarize sessions correctly. Technically, the build now performs a production install in `plugin/` and marks `plugin/node_modules` as distributable, replacing prior bundles that omitted those dependencies; continue watching for build-time drift in dependency sets, potential package-size impact, and whether install/signals are fully visible in mobile clients where hook errors were previously hidden.

Impact

Users and operators on macOS/Windows are less likely to lose prompt sessions silently after upgrades, because the plugin package will now include the runtime modules needed for the worker to start and summarize sessions correctly. Technically, the build now performs a production install in `plugin/` and marks `plugin/node_modules` as distributable, replacing prior bundles that omitted those dependencies; continue watching for build-time drift in dependency sets, potential package-size impact, and whether install/signals are fully visible in mobile clients where hook errors were previously hidden.

What To Watch Next

  • Watch whether claude-mem becomes a repeated pattern.
  • Track follow-up changes around AI Debugging and Error Localization.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: monitor_bundle_omits_updated_dependencies, verify_package_size_is_acceptable_after_shipping_node_modules.
Open Topic TimelineOpen Technical EventOpen Original Sourcemonitor_bundle_omits_updated_dependencies / verify_package_size_is_acceptable_after_shipping_node_modules / track_mobile_clients_not_reporting_hook_failure_signals / ensure_ci_runs_build_packaging_regression_tests

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)

The fix targets issue #2407 by ensuring runtime dependencies are present in packaged plugin releases, preventing worker startup from leaving prompt sessions un-summarized.