SebastianVerified account

Any pluggable interface would likely be very limited to basic AST transforms. Anything more complicated should exist inside of Rome.

Very excited to see RomeJS then! What kinds of more complicated transforms are you hoping RomeJS will enable?

Constant folding and inlining would be the big ones. Depends on how sophisticated any static analysis is and how performantely we can get it working

Definitely tough to do too much, given the constraints of development environments. Does any of the work done on Prepack lend itself to RomeJS’ linting? I’d imagine a good partial interpreter could go a long way towards making JS code less vulnerable

Probably not. Prepack is essentially all ot nothing, and the model doesn't lead to something productionizable. You want something that can compile concurrently, which it can't do. Better off with type information, a control flow graph and some manual transforms

Do you see any shortcomings of a concurrent approach?

Nope. It’s essential for performance, and thinking about each specific step of the analysis as a cachable artifact, makes concurrency easy since you can easily pass it around etc

What if the build system was run as a service (a codesandbox integration, for example)?