SebastianVerified account

This is a collection of my tweets over the past ~2 years about a project I've been working on. Time and work fluctuated over that period. It was called Sonic, then Hydra. Now it's called Rome. It's a JavaScript toolchain. It has zero dependencies, every thing is custom.

Will the RomeJS compiler be pluggable like Babel's. And if so, how will the DX differ? There are some cool challenges, such as referencing the ASTs of other files. Also, directly mutating nodes often gets their paths out of sync. How do you safeguard against this in RomeJS?

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