Replies: 7 comments 5 replies
-
See pegjs/pegjs#667 |
Beta Was this translation helpful? Give feedback.
-
Hi. I just migrated the plugin ts-pegjs to use peggy. Regards, |
Beta Was this translation helpful? Give feedback.
-
Hi guys, great work with Peggy. I added a message (with dramatic caption 😄) to the readme of my PEG.js extension and suggest to switch to the peggy extension. |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
See #193 |
Beta Was this translation helpful? Give feedback.
-
When v1 is safely out of the door and we're happy with it we should start reaching out to the broader ecosystem to encourage people to switch over. There's a bunch of pegjs plugins, prettier plugins and syntax highlighting rules that are in active use and it'd be great if we could support them.
At some point we will also need to introduce our own file extension, but
.pegjs
should continue to work for the foreseeable future.We should also write an announcement that explains the reasons for the fork (in a tactful way), and write some simple instructions to make switching over easier. It may be possible to get npm to deprecate the pegjs package if David can talk to them, but I don't know whether that's desirable or whether he'd be comfortable doing so - it would help with adoption though.
It would also be great if we can get some of the more prolific / well known users of PEG.js to support this effort. I know @mikeal uses it on some of his projects, there are likely many more.
We should also look at the dependency graph on npm and github and reach out to the bigger projects that consume it encouraging them also to make the switch.
Beta Was this translation helpful? Give feedback.
All reactions