-
Notifications
You must be signed in to change notification settings - Fork 4
CS2 Discussion: Project: Make it extensible or pluggable #4
Comments
Sounds good. We should try and stick to a standard format for the AST. The de facto standard is ESTree, that grew out of work done at Mozilla. They have excellent contributors, and seem to be on top of their ES6-7 support. We may have less work to do than we thought, especially if we fork Redux. |
One thing to think about could be plugging directly into Babylon, and leaning on Babel to do provide the plugin support. I haven't looked into this in-depth, and babylon itself isn't pluggable yet:
Since (IIRC) the grammar of CSRedux is EBNF or similar, this might not be terrible to implement. |
I was lukewarm on this idea until I read #21, now I see it more like the modularity of XMPP (Jabber). I'd be happier still if modules also had a stability index akin to the Node stability index, designated by the core community and defaulting to experimental when no such designation has been given. Maybe the index would look something like...
|
This is only relevant if we have people willing to devote serious time to this project. See #27 |
Closing as this looks generally out-of-scope. I know @carlsmith has begun work on a separate project which may allow this, however. See https://github.com/carlsmith/shalt/ for that. |
This issue was moved to jashkenas/coffeescript#4903 |
To make this transpiler pluggable, to be possible to plug parser extensions, and plug external AST to JS code generator.
With this, initiatives like IcedCoffee, ember-script, and ES(next) support could survive integrated to this CS ecosystem. Develop the support to the next ES will not hurt, and independent plugins will prove good ideas to make JS features CSish.
The text was updated successfully, but these errors were encountered: