{"version":"2.1.271","anchor":"bun-transpile-errors-for-plugin-source-now-wrapped-instead-o","canonical_anchor":"bun-transpile-errors-for-plugin-source-now-wrapped-instead-o","heading":"Bun transpile errors for plugin source now wrapped instead of thrown raw","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/bun-transpile-errors-for-plugin-source-now-wrapped-instead-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Bun transpile errors for plugin source now wrapped instead of thrown raw\n\nPlugin transpile failures now surface as a proper error instead of a raw crash\n\n**What**\n\nWhen Claude Code transpiles a non-JavaScript plugin source file and the transpile step (via Bun's transpiler) fails, that failure is now caught and rethrown as a proper internal error object, instead of letting the underlying tool's raw exception propagate up unhandled.\n\n**Why**\n\nThis means a broken plugin source file now produces a clearer, consistent error rather than an unhandled crash from the underlying transpiler.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}