`minify` edits the regex (incorrectly)

[CptMeatball]

When minifying a JS file with a (certain) regex, it changes the regex to a regex that does something different.

minify file.js > min.js

The following regex:

const regex = /^([A-Z0-9_+-]+\.?)*[A-Z0-9_+-]@([A-Z0-9][A-Z0-9-]*\.)+[A-Z]{2,}$/i;

is converted to:

const regex = /^([\w+-]+\.?)*[\w+-]@([\da-z][\da-z-]*\.)+[a-z]{2}$/i;

Running terser file.js -o min.js --compress --mangle (terser@5.31.3 in node@22.11) directly does not produce the same result.

[coderaiser]

Could you please provide simpler regexp? What is wrong optimized form?

[CptMeatball]

The regexp itself is an expression for checking if it is a valid email address. The expression itself isn't great, but the issue is that minify changed the expression, resulting in unexpected behavior in production builds.

I sadly don't have an alternative regexp, but the issue revolves around the last part of the regexp, {2,} is replaced by {2}, which has a different meaning.

Example:
This is valid following original exp but not for the minified one as the last group should be 2 characters in the minified one.

foo@gmail.com

Hope it helps. For now we implemented terser and lightning-css directly as this better fits our current needs.

[coderaiser]

Just fixed with https://github.com/putoutjs/printer/releases/tag/v14.8.0, please re-install Minify. Is it works for you?