Futago-za Ryuu

```js int = [0-9]+ { return hex(int) } commaExpr = int '-' int '-' int { return match().join('') } ``` It wouldn't be a syntax change, it would be another...

Yes, that's what I've been saying :sweat_smile:

To be entirely honest, aside from updating Unicode support for the [PEG.js grammar parser](https://github.com/pegjs/pegjs/blob/master/src/parser.pegjs) and the [JavaScript example](https://github.com/pegjs/pegjs/blob/master/examples/javascript.pegjs), I have little to no knowledge about Unicode, so am currently unable...

@drewnolan Thanks for the heads up 👍

This behaviour is intentional, see: 1) issue #368 2) pull request #415 3) https://github.com/pegjs/pegjs#error-messages. I agree with you though, it is confusing, but will only look into this when I'm...

Hmm, a slight oversight that seems to have gone unnoticed for years 😆 Will try and fix this before 0.11 comes out officially. Currently, I'm swamped with work while working...

Node.js use's the commonjs format, so yes, you can think of them as the same in this context. The online version is using PEG.js 0.9, which doesn't have the format...

@bd82 UMD is already supported

I'm moving this to 1.0 as it's hard to find one that suites the above conditions, although I'm leaning towards a custom fork of [Commander.js](https://github.com/tj/commander.js) with the bug mentioned fixed....

I think it's worth adding a non-`eval` alternative for Content Security Policy compatibility; will see into this at some point before 0.12 by adding another bundle (maybe named `dist/peg.csp.js`) via...