CS2 Discussion: Project: Make it extensible or pluggable

[coffeescriptbot]

From @aurium on July 12, 2016 20:8

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.

Copied from original issue: coffeescript6/discuss#4

[coffeescriptbot]

From @carlsmith on July 14, 2016 13:40

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.

[coffeescriptbot]

From @rattrayalex on July 14, 2016 19:40

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:

Significant diversions are expected to occur in the future such as streaming, EBNF definitions, sweet.js integration, interspacial parsing and more.

Since (IIRC) the grammar of CSRedux is EBNF or similar, this might not be terrible to implement.

[coffeescriptbot]

From @rdeforest on August 23, 2016 15:56

I was lukewarm on this idea until I read coffeescript6/discuss#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...

idx	title	description
-1	rejected	incompatible with project tech or philosophy
0	deprecated	not supported
1	experimental	under development
2	testing	stabilizing
3	stable	official, stable, standard part of project
4	core	critical bugs and security fixes only

[coffeescriptbot]

From @GeoffreyBooth on August 23, 2016 16:47

This is only relevant if we have people willing to devote serious time to this project. See coffeescript6/discuss#27

[coffeescriptbot]

From @rattrayalex on September 9, 2016 15:32

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.