{"version":"2.1.269","anchor":"plugin-hooks-module-scan-enforces-that-nextto-targets-be","canonical_anchor":"plugin-hooks-module-scan-enforces-that-nextto-targets-be","heading":"Plugin hooks-module scan enforces that next.to() targets be statically discoverable","tier":"internal","area":"Plugin Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/plugin-hooks-module-scan-enforces-that-nextto-targets-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Plugin hooks-module scan enforces that next.to() targets be statically discoverable\n\nPlugins that call next.to() with a hooks module name Claude Code can't find in the code are now rejected\n\n**What**\n\nPlugin code can call `next.to(\"name\")` to hand off to a named hooks module (a plugin file that reacts to Claude Code events). A new check now scans plugin code ahead of time to make sure that name is spelled out literally somewhere it can find. If the target can't be located this way, the call now throws an error instead of proceeding.\n\n**Why**\n\nThis closes off hooks-module handoffs that can't be verified in advance, which previously could fail unpredictably at runtime. Plugin authors need to name `next.to()` targets literally so the static scan can find them.\n\n- Area: Plugin Hooks\n- Names: `next.to`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}