{"version":"2.1.242","anchor":"plugin-validate-inspects-hooks-modules-instead-of-a-declared","canonical_anchor":"plugin-validate-inspects-hooks-modules-instead-of-a-declared","heading":"\/plugin validate inspects hooks modules instead of a declared capabilities list","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/plugin-validate-inspects-hooks-modules-instead-of-a-declared","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### `\/plugin validate` inspects hooks modules instead of a declared capabilities list\n\nPlugin validation now loads your hooks modules and reports what they hook; the capabilities field is ignored.\n\n**What**\n\nValidating a plugin's hooks.json now loads each JavaScript hooks module it names, refuses any path that points outside the plugin directory, and reads the module to report which events it hooks and which plugin APIs it calls. A `capabilities` field in the file is now reported as ignored and safe to delete.\n\n**Details**\n\n- A plugin naming more than one hooks module is reported as refused by the loader.\n\n**Evidence**\n\n`'capabilities' is no longer read`\n\n- Area: Plugins\n- Names: `\/plugin validate`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}