regjsparser
regjsparser copied to clipboard
Parsing the JavaScript's RegExp in JavaScript.
Inside `parseAtomAndExtendedAtom`, `(?` used to be searched from the start of the string, rather than from the current position. So, trying to parse an expression containing nested lookarounds and inline...
The type previously did not allow the reference to be an index type reference if `namedGroups` was enabled
https://people.mozilla.org/~jorendorff/es6-draft.html#sec-get-regexp.prototype.sticky This doesn’t affect parsing, so it seems fairly easy to do.
I started working on a package for Debian, and wrote a [manpage for regjsparser](https://anonscm.debian.org/cgit/pkg-javascript/node-regjsparser.git/tree/debian/regjsparser.1) ; if you're interested, it's under BSD (see debian/copyright).
This came to my mind when preparing the presentation for Amsterdam.JS: Currently there is a special `type="dot"` for things like `/./`. Per see there is nothing wrong with this, but...
Currently the API is `parse(string)`, meaning `parse` accepts a single string representing a regular expression. It should be possible to specify which flags apply to the regular expression, since they...
\to @d10 @mathiasbynens @termi Hi there, while brainstorming about my talk in Amsterdam about RegExp.JS I think more and more about the "family" of JS-RegExp tools we build so far...
This was brought up before and also arises in #54. The idea is to have a verbose mode, which splits out the current from of the AST. If the `verbose`...
Here’s the current AST for `[a-z]`: ``` json { "type": "characterClass", "body": [ { "type": "characterClassRange", "min": { "type": "value", "kind": "symbol", "codePoint": 97, "range": [ 1, 2 ], "raw":...
After all the PRs are done we should look at providing documentation to the AST format.