FAQ

Why not build our own parser?

You can, but it is much harder than it first looks. Regex flavors diverge in subtle ways, edge cases pile up quickly, and keeping behavior aligned with engines is a long-term maintenance commitment.

Is it production-ready?

Yes. It is already used in production by regex101 and exercised at large scale.

Does it support incremental parsing?

No, by design. It reparses full patterns in linear time, which keeps performance predictable and implementation complexity lower.

Is AST documentation available?

The AST is fully typed in TypeScript today. Formal written AST docs are planned.

Does it include linting or ReDoS detection?

Not yet. The current focus is fast, engine-accurate parsing with strong typed output.

Can it be used in browser and Node.js?

Yes. It supports both runtimes and ships for both ESM and CJS.