To begin, check out the website.
Read the blog or the changelog to learn about new features.
Pre-built binaries can be found on the releases page.
Pomsky can also be installed from source via cargo with cargo install pomsky-bin.
Pomsky is currently compatible with PCRE, JavaScript, Java, .NET, Python, Ruby and Rust. The regex flavor must be specified during compilation, so Pomsky can ensure that the produced regex works as desired on the targeted regex engine.
Note: You should enable Unicode support in your regex engine, if it isn't enabled by default. This is explained here.
Pomsky aims to be as portable as possible, polyfilling Unicode and unsupported features where feasible. That said, there are some cases where portability is not possible:
-
Some features (e.g. lookaround, backreferences, Unicode properties) aren't supported in every flavor. Pomsky fails to compile when you're using an unsupported feature.
-
\b(word boundaries) are not Unicode aware in JavaScript. Pomsky therefore only allows word boundaries when Unicode is disabled. -
\win .NET handles Unicode incorrectly, with no way to polyfill it properly. This means that in .NET,[word]only matches theL,Mn,Nd, andPcgeneral categories, instead ofAlphabetic,M,Nd,PcandJoin_Control. -
In .NET,
.,Codepointand character classes (e.g.[Latin]) only match a single UTF-16 code unit rather than a codepoint. -
[space]matches slightly different code points in JavaScript than in Java. This will be fixed. -
Backreferences behave differently in JavaScript and Python when the referenced group has no captured text. There is nothing we can do about it, but we could add a warning for this in the future.
Never compile or execute an untrusted Pomsky expression on your critical infrastructure. This may make you vulnerable for denial of service attacks, like the Billion Laughs attack.
Pomsky looks for mistakes and displays helpful diagnostics:
- It shows an error if you use a feature not supported by the targeted regex flavor
- It detects syntax errors and shows suggestions on how to resolve them
- It parses backslash escapes (which are not allowed in a Pomsky expression) and explains what to write instead
- It looks for likely mistakes and displays warnings
- It looks for patterns that can be very slow for certain inputs and are susceptible to Denial-of-Service attacks (coming soon)
I wrote an in-depth comparison with similar projects, which you can find here.
The Code of Conduct can be found here.
You can contribute by using Pomsky and providing feedback. If you find a bug or have a question, please create an issue.
I also gladly accept code contributions. More information
Dual-licensed under the MIT license or the Apache 2.0 license.