{"version":"2.1.275","anchor":"hooks-modules-must-now-be-named-like-code","canonical_anchor":"hooks-modules-must-now-be-named-like-code","heading":"Hooks modules must now be 'named like code'","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/hooks-modules-must-now-be-named-like-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Hooks modules must now be 'named like code'\n\nPlugin hook modules must now use a recognized code file extension or they won't load\n\n**What**\n\nFor plugins, the `module` field in `hooks.json` (the file that registers a plugin's hooks, which are scripts that run at specific points in Claude Code) must now point to a file with a recognized code file extension, and every file it imports from the plugin must too. Files with other extensions are rejected and simply not loaded, and a specific error message now lists which extensions are valid.\n\n**Why**\n\nThis catches misconfigured or mistyped plugin hook files early, with a clear error instead of a silent failure to load.\n\n- Area: Hooks\n- Names: `hooks.json`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}