Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.271,
Internal ChangesSection of the release
What
Claude Code runs some code inside a Node VM context (an isolated JavaScript sandbox), which needs a workaround so instanceof Error checks work correctly across that boundary. That workaround now only kicks in when the check is against Error itself; checks against subclasses of Error fall back to JavaScript's normal built-in behavior instead of being overridden.
Why
The previous version overrode the check unconditionally, which could give wrong answers for custom error subclasses. Narrowing it to just Error makes instance checks behave correctly in more cases.
