{"version":"2.1.246","anchor":"hooks-modules-are-read-and-linked-before-they-run-with-file-","canonical_anchor":"hooks-modules-are-read-and-linked-before-they-run-with-file-","heading":"Hooks modules are read and linked before they run, with file and size caps","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/hooks-modules-are-read-and-linked-before-they-run-with-file-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Hooks modules are read and linked before they run, with file and size caps\n\nHooks modules now load up front and refuse if they link too many files or grow too large.\n\n**What**\n\nA hooks module's imports are now resolved and read up front rather than during evaluation, and two limits apply to every load: a module may link at most a fixed number of files, and the combined size of all its sources has a byte ceiling. Exceeding either refuses the load with its own message. No flag turns this off.\n\n**Details**\n\n- Imports are pre-read into a map keyed by the importing file plus the exact import text, so the same spelling from different files resolves independently.\n- Refusing an import, spotting a module importing itself, and resolving an import path all moved into shared helpers new in this build.\n\n**Evidence**\n\n`is past the `\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}