{"version":"2.1.271","anchor":"hooks-modules-can-now-declare-load-order-dependencies-on-eac","canonical_anchor":"hooks-modules-can-now-declare-load-order-dependencies-on-eac","heading":"Hooks modules can now declare load-order dependencies on each other","tier":"use","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/hooks-modules-can-now-declare-load-order-dependencies-on-eac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Hooks modules can now declare load-order dependencies on each other\n\nHooks modules can now declare dependencies that control their load order\n\n**What**\n\nHooks modules (packages of automated scripts that run at certain points in Claude Code) can now declare a `dependencies` field in their manifest, saying which other hooks modules they depend on. Claude Code computes a load order from these dependencies so that a module loads after the modules it depends on, within the same tier. If two modules depend on each other in a cycle, Claude Code detects this, refuses to load them that way, and shows a warning.\n\n**Why**\n\nThis lets hooks modules that build on each other load in a predictable, correct order, and prevents a circular dependency from causing undefined or broken behavior.\n\n- Area: Hooks\n- Names: `dependencies`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}