SebastianVerified account

@sebmck in Rome, have you abstracted away the 'host environment' in any way to make the toolchain available in contexts like the browser? Certainly would be amazing to have a tight, UX friendly ecosystem like that in the browser.

Yeah, enough is abstracted that it could work outside of Node. I’ve minimised my usage of Node APIs. There’s abstractions around the parts they matter. In fact, it would be easy to make Rome has WebWorkers for workers instead of spawning processes. The RPC is very agnostic.

Could also prettily run in Deno then?

Potentially*

Yep

In fact, I was (sort of still am), considering bundling the Rome CLI with my own version of Node/whatever. Would make it easy to use Rome outside of the Node-ecosystem. Would also allow easy distribution. Similar mode to Yarn, available everywhere: homebrew, apr-get, rubygems etc

Interesting! If you don't mind me asking here, will Rome also be pluggable with custom AST transforms? Or is the plan to lock it down to support only stable syntax?

Not sure how to handle plugins. It’s definitely possible and I’m designing everything to allow it. Hard part is figuring out how to expose it without widening the API surface area. Likely wouldn’t be available for any initial open source release (if there is one).