[Bug] terser incorrectly removes ReferenceError for computed property using class name #1593

Terser incorrectly optimizes a class with a computed property key when the key references the class name itself. This results in an output that no longer throws a ReferenceError.

terser input:

I used terser REPL to reproduce the bug with the following input:

class x { [ ! { x } ] ; }
new x

This input script throws ReferenceError:

❯ node input.js
class x { [ ! { x } ] ; }
                ^

ReferenceError: Cannot access 'x' before initialization

Node.js v22.9.0

terser output

class s{[!1]}new s;

The output executes normally without throwing an error.