I built a regex tester that tells you what your pattern actually does
TL;DR: Regex is powerful and unreadable. I built a tool that takes any regex pattern and breaks it into plain English, piece by piece. Below is how the explanation engine works, plus the three patt...

Source: DEV Community
TL;DR: Regex is powerful and unreadable. I built a tool that takes any regex pattern and breaks it into plain English, piece by piece. Below is how the explanation engine works, plus the three patterns every dev should actually understand. I wrote this regex last year: ^(?=.*[A-Z])(?=.*[0-9])(?=.*[!@#$%^&*])[A-Za-z0-9!@#$%^&*]{8,}$ Four months later I came back to that codebase. Read the pattern. Had absolutely no memory of what it does or why I wrote it that way. And I wrote it. This is the universal regex experience. You understand it for about 20 minutes after writing it, then it becomes ancient hieroglyphics permanently. So I built a regex tester that doesn't just tell you "match" or "no match" — it explains every piece of the pattern in actual human words. You paste a regex, it tells you what each part does. Here's how. How the explanation engine works Collectively, the regex syntax boils down to maybe 15-20 token types. Anchors, character classes, quantifiers, groups, loo