Release the parser as a separate npm package

[mathiasbynens]

• [x] release the parser as a separate npm package: done https://github.com/jviereck/regjsparser
• [ ] use it as a dependency for regexp.js

[jviereck]

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 the test262 suite).

Mathias, can you take a quick look if this looks good and if this is what you are looking for? Happy to change things around and make your life easier :)

For now, I don't want to make regexp.js-parser a dendency of RegExp.JS. Once I got feedback from you, that the basic repo shape is "okay", I will change things around.

[mathiasbynens]

It sure looks alright to me :) Thanks for doing this!

[mathiasbynens]

How about a simpler project name? Something like regexparse would be a bit easier to type/remember. (It would also help when using the binary, as it inherits the npm project name.)

[jviereck]

Agreed that the project name is too complicated.

To keep the "flavor" of RegExp.JS and strengthen the JS part, how about regjsparse?

[mathiasbynens]

I prefer regexparse as it’s more obvious, but sure :) Anything that gets rid of the . and - in the name is a win as far as I’m concerned!

[jviereck]

Renamed the project.

  RegExp.JS - Parser is dead - long live RegJSParser!

https://github.com/jviereck/regjsparser

[mathiasbynens]

Yay! Let’s publish it on npm under this name too, before people start relying on the old name.

[jviereck]

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 seems down fro me, so I cannot verfiy at the moment.

[jamestalmage]

Any reason you're not using the separate project as a dependency yet?

[jviereck]

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 output has changed compared to what is used in the tree here.