6 ms·

Thanks for the feedback! Yea, you're totally right. I'll update the docs to reflect this. > why not just wrap vanilla JS regex, rejecting patterns including th

Thanks for the feedback! Yea, you're totally right. I'll update the docs to reflect this. > why not just wrap vanilla JS regex, rejecting patterns including them? Yea! I was thinking about this too actually. And this would solve the problem of being server side only. I'm thinking about making a new version to do just this. For a pattern rejecting wrapper, how would you want it to communicate that an unsafe pattern has been created.

0points 1y ago
> And this would solve the problem of being server side only. Server-side? You should look into how you compile your rust into wasm
DemocracyFTW2 1y ago
> how would you want it to communicate that an unsafe pattern has been created Given this is running on a JS engine, an error should be thrown much as an error will be thrown on syntactically invalid regexes in the source. Sadly, this can't happen a module load / compile time unless a build step is implemented, complicating the matter; but on the other hand, a regex that is never used can also not be a problem. The build step could be stupidly simple, such as relying on an otherwise disallowed construction like `safe/[match]*me/`.