James Brundage

The various command types in Irregular should be formalized in it's manifest. See

Should match console progress information, e.g. https://github.com/microsoft/terminal/issues/6700#issue-646668791

There should be a regex generator the matches an identifier in one or more programming languages. It should effectively have two parts: IdentifierStart IdentifierSequence

Irregular should be able to convert regular expressions into [ECMAScript RegEx](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions). This would Compress-Regex and then flag certain portions of the RegEx if they were incompatible with ECMAScript Regex.

A Parser File Should represent a way to parse input. Tentatively, it should support the following file patterns: * `.parser.ps1` * `.irregular.parser.ps1` A parser would be "valid" under a few...

If even some of the expressions generated from Irregular can be exported into a form JavaScript will know and love, this is a huge win.

Who says a container can't look good? * [ ] #386 * [ ] #387 * [ ] #389 * [ ] #390 * [ ] #391