You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using terser to minify a library meant to be used by other developers.
The fact that terser mangles the class names in the demonstrated manner makes so that users of our library will see minified classnames when inspecting objects in the dev inspector in chrome, for example. Chrome (and node, and others probably too) use the var name to assign a name to the class.
The demonstrated mangling breaks that. I would expect keep_classnames to prevent this, just as it does in the direct class definition (Foo). These statements (var X = class {}) are generated by esbuild during bundling, so we don't have much control over that.
The text was updated successfully, but these errors were encountered:
This is very inconsistent with keep_fnames which works as you expect.
The second case is definitely valid as well, and should apply to keep_fnames too. With keep_fnames/keep_classnames, moving a class/function should either retain its .name property or not happen at all.
Bug report or Feature request?
Bug Report
Version (complete output of
terser -V
or specific git commit)terser 5.26.0
Complete CLI command or
minify()
options usedOptions:
Input:
terser
output or errorExpected result
We are using terser to minify a library meant to be used by other developers.
The fact that terser mangles the class names in the demonstrated manner makes so that users of our library will see minified classnames when inspecting objects in the dev inspector in chrome, for example. Chrome (and node, and others probably too) use the var name to assign a name to the class.
The demonstrated mangling breaks that. I would expect
keep_classnames
to prevent this, just as it does in the direct class definition (Foo
). These statements (var X = class {}
) are generated by esbuild during bundling, so we don't have much control over that.The text was updated successfully, but these errors were encountered: