Joe Hildebrand

here are a few options (assuming the output of peggy is `grammar.js`): 1. You can use [ts-pegjs](https://github.com/metadevpro/ts-pegjs#readme), which you may or may not find worth the extra complexity. 2. You...

One possible approach if someone takes this on: - Make sure that the types in peg.d.ts are appropriate for generated parsers - Emit TypJSDoc comments that use `import('peggy')`

This no longer depends on #60. This could just be a download link to https://peggyjs.org/vendor/peggy/peggy.min.js, but I want to make it clear that people should be caching it from unpkg...

I am strongly in favor of moving to Monaco, after having tried it on another project.

I'm fine with the current approach. If anyone feels strongly about prettier, please send a PR.

I'd really rather not change all the formatting at this point, but if you can make prettier get "close enough" to what we currently have, I guess I'd look at...

I really don't want to change the eslint rules unless we get enough benefit out of it. I really don't see prettier as a benefit, since I have my editor...

I would accept a patch that adds `.vscode/` to git .gitigore file. I just realized that I've got it in my `~/.gitignore_global` file.

That sounds like a workable plan. `peggyjs.peggy-language` has a circular dependency on peggy, so when adding new features to the examples, we'll see a few issues. I *think* I'm willing...

Fixed in #432.