Closed dariusk closed 8 years ago
It's worth noting that I've not updated the npm library to new Tracery yet - that is not quite trivial to do, but is on my list (as then I can upgrade CBDQ)
If there's anything I can do to make porting eaiser, too, lmk. I don't know what the additional constraints are, but if I know I can make sure I support them going forward. On Nov 30, 2015 4:04 PM, "George Buckenham" notifications@github.com wrote:
It's worth noting that I've not updated the npm library to new Tracery yet
- that is not quite trivial to do, but is on my list (as then I can upgrade CBDQ)
— Reply to this email directly or view it on GitHub https://github.com/galaxykate/tracery/pull/8#issuecomment-160654963.
Opened up a new issue to chat about this on: https://github.com/galaxykate/tracery/issues/9
I had copy/pasted the example grammar and was getting tons of errors -- I thought it was my code but it turns out the grammar was using outdated syntax for saving data. Updating that here with something from the tutorials that works in both the browser and Node.js libs.
I also added a link to @v21's Node lib. I have a pending pull request over there that would make it very clear how to install the library via
npm
.