regex not detected results in broken JS output

[futtta]

Trying to minify this extract of real-world 3rd party JS

x=navigator.vendor,S=navigator.userAgent,C=y(e=>/Edge\/|Edg\//.test(e||S)),le=y(e=>/Firefox/.test(e||S)),ue=y(e=>/Trident|MSIE/.test(e||S)),w=y(e=>/Opera|OPR/.test(e||S)),de=y((e,t)=>(/Chrom/.test(e||S)&&/Google/.test(t||x)||/CriOS/.test(e||S))&&!C(e)&&!w(e)),fe=y(e=>/Chrom|Applechromium/.test(e||S)),pe=y((e,t)=>/Safari/.test(e||S)&&/Apple Computer/.test(t||x)&&!C(e)&&!w(e)),me=y(()=>/WebKit/.test(S)),he=e=>{let t=e.indexOf(Version/); nextline="hi";

results in
x=navigator.vendor,S=navigator.userAgent,C=y(e=>/Edge\/|Edg\ nextline="hi"

due to the regex not being properly detected.

in JSMin.php changing the first test in the isRegexpLiteral function from

        if (false !== strpos("(,=:[!&|?+-~*{;", $this->a)) {
            // we can't divide after these tokens
            return true;
        }

into

        if (false !== strpos("(,=:[!&|?+-~*{;>", $this->a)) {
            // we can't divide after these tokens
            return true;
        }

fixes the problem, but not sure if this is the proper/ best way to solve this? can we divide after > ?

[aokod]

yes, this appears to be a safe way to solve the described problem and no, you cannot have division immediately after > in JS. division always has an operand between > and / (for example, a > b / c). the only case i can think of where > precedes / is in arrow functions (=>), however, since division requires a left operand, / cannot start an expression as division, and so it will always be a "literal" regular expression