Julian Viereck

Hi Chelsea, thanks for the quick reply! Sure, more than happy to make a PR. Is there an automated way to run a unit test suite to avoid the PR...

Hi Chelsea, thanks for your reply and sorry for getting back to it after a so long delay. > the best thing to do is run each of the mjc...

(Sorry, GitHub was doing something wired and saved the first comment before I had finished writing. If you don't see a "Thoughts?" at the end of the previous post, then...

See https://npmjs.org/package/regexp.js-parser. I've added you to the list of collaborators at https://github.com/jviereck/regexp.js-parser Also setup Travis testing and added a few more RegExp to test the parser against (took them from...

Agreed that the project name is too complicated. To keep the "flavor" of RegExp.JS and strengthen the JS part, how about `regjsparse`?

Renamed the project. ``` RegExp.JS - Parser is dead - long live RegJSParser! ``` https://github.com/jviereck/regjsparser

> Yay! Let’s publish it on npm under this name too, before people start relying on the old name. I unpublished the old one and published the new one. npmjs.org...

> Any reason you're not using the separate project as a dependency yet? Mostly lack of motivation and time. Using the separate parser project won't be trivial as the parser...

@PabloK, thanks for reporting this! Can you share a link or the document with me that fails for you? Then I am more than happy to take a look at...

@PabloK do you have a working example such that I can play with the changes you have proposed in #10? Otherwise it's hard for me to judge what is the...