I'm gonna be That Other Guy and say that the date and phone regex are respectively english-language and US specific. So it's common for a narrow definition of common.
> There is always a well-known solution to every human problem — neat, plausible, and wrong.
often paraphrased as "For every complex problem there is an answer that is clear, simple, and wrong."
> um 6:00 am 05.12. (at 6:00 on 12/05/..)
If i read it correctly, the time regex would extract "6:00 am" as time, but the "am" is wrong (German uses 24h format).
Simple regular expressions can be good enough if you're aware of the domain restriction though.
This is an excellent point. Petty substitutions like verbal expressions might be useful if you're just getting started, but ultimately it's a crutch and it's best just to learn pure regular expressions. They're not that difficult.
Same with bundling a ton of dependencies. Lots of people (especially contemporary programmers, primarily web developers) seem to be deathly afraid of writing custom code to handle a job. It's not "reinventing the wheel", it's implementing logic easily extensible within your application without the hassle of upstream, especially if you're only using a small portion of a library or framework. Using 15 libraries for a 600-line script isn't best practice, it's cowardice.
> Please note that this module is currently English/US specific.