Instruct terser to not mangle class names so Catalyst works #1314
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@langermank and I have been running into weird issues viewing Lookbook previews where JavaScript for Catalyst components is throwing uncaught errors. The problem turns out to be that terser mangles class names to make them shorter. Catalyst depends on class names to automatically define custom elements. In their docs, the terser section says to pass a special option that disables class name mangling. Adding this to my local rollup config fixes the problem.