Fábio Santos

I managed this reproduction with less elements ```js const testVarOne = 'Please preserve this'; const usedOnce = testVarOne const usedTwice = testVarOne class MyElement { static { // class refers...

Seems to have been fixed in https://github.com/terser/terser/commit/437be8bef85bf810d66ab1eb7a802f28129711cf

I notice you're talking about chunks, so I assume you're using webpack. Webpack doesn't use the nameCache option, which is why mangling properties doesn't work across chunks. But it may...

There's something that Terser and the bundler plugins can do together, which is to provide a pre-step to gather all properties, and create a name cache, and then use it...

Ok, I understand now. Terser finds all annotated properties, but it doesn't store them in nameCache for subsequent runs. This might not be possible to fix completely. Consider this example:...

There's a new property, so tests are failing, just like in the [original package](https://github.com/jridgewell/source-map/commit/2242e904ea7f87d0b518628866805feec0b233f5#diff-4f18de29c23207aca044431ae60e596bd2cbd674c47a7cc1ee1e61a0a8e5bb1dR26) they need an update.

What should be the output for people who wrote `assert`? Should it be garbage-in-garbage-out or always output `with`? `assert` wasn't JS syntax proper, but it might be supported by some...

This is why I should always wait for stage 4 :)

You are correct that the minifier shouldn't convert between them, at least in theory. I'll wait for Stage 4 to implement, otherwise I might have to support 3 different versions...

This became stage 4, so I implemented it, will release today or tomorrow