Release on NPM

[TheKnarf]

While you do state that it's not production ready yet, I've enjoyed using it on a few prototypes I've made. Would it be possible to release the 0.1.0 package on npm so that I can reference that in case I publish any of my prototypes?

Currently, this is the way I reference it (in my package.json), meaning that I can't reference a given version:

  "dependencies": {
    "gruffalo": "git+https://github.com/no-context/gruffalo.git"
  }

I think that the 0.1.0 version is enough indication that it's not production ready yet, but some people might still want to use it never the less. I at least do not know of any other RNGLR parsers in JavaScript.

[tjvr]

Thanks for your interest in this project! I don't believe anyone else has used it yet 😀

NPM lets you specify a commit hash in your package.json, so you can depend on no-context/gruffalo#<short-SHA> for example.

However, this project really is little more than a prototype. I'm hoping to merge it with my other parser project before taking it further, let alone publishing it on NPM 😊

_{Sent with GitHawk}

[TheKnarf]

Using the trick of referring directly to a commit using an SHA sounds like a good tip.

While I can understand the hesitance to release a project you still feel is in alpha stage, I personally think that it is good enough to release a 0.1.0 or 0.0.1 version. That way you get to keep the Gruffalo name on npm and make it easier for anyone currently playing around with it to upgrade to a newer version once you release an update.

Either way, feel free to close this issue once you make a final decision.

[tjvr]

I at least do not know of any other RNGLR parsers in JavaScript.

Out of interest, how did you find this project? 🙂

[TheKnarf]

Out of interest, how did you find this project? 🙂

@tjvr I read a few papers on parsing, among them the Right nulled GLR parsers paper and googled around to see if anyone had implemented it in JS yet.