he/him 
@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.
-
It would be a nice touch to provide tooling support for future Rome devs (not users) to prevent them from reaching for host-specific APIs. Each plugin that encodes a new host-specific API narrows where the tool can be used. Rome could give tools to devs to stay 'pure'.
I've tried to make things pretty lightweight. The current list of Node built-ins that Rome uses are: stream: 8 readline: 2 util: 4 net: 4 child_process: 4 crypto: 4 path: 22 fs: 16 module: 1 zlib: 1 os: 3 inspector: 2
-
-
Rome has zero third party dependencies. A bunch of those modules don't have any runtime Node behaviour, so could easily be mocked, or otherwise have a custom Rome variant of those modules.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.