{"version":"2.1.309","anchor":"plugin-module-linking-handles-stack-overflow-gracefully","canonical_anchor":"plugin-module-linking-handles-stack-overflow-gracefully","heading":"Clearer error when a plugin file is nested too deeply to load","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/plugin-module-linking-handles-stack-overflow-gracefully","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Clearer error when a plugin file is nested too deeply to load\n\nA plugin file whose code or imports nest too deeply now fails with a plain explanation instead of a raw engine error\n\n**What**\n\nWhen Claude Code loads a plugin file, it also links in the other files that file imports. If that linking runs the JavaScript engine out of room, Claude Code now reports: \"the engine ran out of stack linking the file and its imports (code nested too deep, or a chain of imports too long)\". Before, only this kind of failure while loading the file itself was reported.\n\n**Why**\n\nPlugin authors get an error that points at the likely cause, deeply nested code or a long chain of imports.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}