It only will do this if you have the option selected at the bottom:
Disallow insecure . and [^...] in /RegExp/
From the docs:
true if . and [^...] should not be allowed in RegExp literals. These forms should not be used when validating in secure applications.
So the answer your question, if you start a regex with ^
and it's checked, yes it'll throw the error every time. The issue is with unicode characters, you're allowing pretty much anything in there and there's potential for security issues, or validation bypassing issues. Instead of disallowing something (which can be bypassed), allow only what characters are valid.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…