he/him 
Recent addition the Rome CLI output is that it will soft wrap logs which is super nice. Note the "The likely cause" line.
Show this thread
Debugging Rome with Rome is pretty awesome. No idea how I would have debugged issues like this in the past.pic.twitter.com/f13r4qC1GW
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
your profile pic lmfao
- 4 more replies
New conversation -
-
-
Speaking of simplifying error language, the advice is pretty intuitive, but the error message is pretty cryptic. Can probably improve upon “binding” and “module ordering”.
-
Yeah it’s had to encapsulate. I tried to word it without having to explain module cycles but I don’t think it’s possible.
- 1 more reply
New conversation -
-
-
What's the end goal of Rome? Is it supposed to be a build tool like Webpack or something akin to Babel? It's cool to you're making progress on it though.
- End of conversation
New conversation -
-
-
Based on that screenshot it looks like Rome has a concept of entry points. This is great for error messages! Other module cycle detecting tools I've seen don't do this and therefore can't correctly tell you which modules will be uninitialized.
-
This is built into the bundler, rather than being a separate tool
End of conversation
New conversation -
-
-
Will Rome be type-aware or will it support plugging in Flow or TS so type information can be provided to lint rules? Will the bundler have Prepack features in? (Which would be another source for types.) TYPES! TYPES! TYPES!
-
I want it to be type aware. It won’t consume type information from other tools though. Way too hard to integrate, impossible to factor into caching without extremely strong assumptions. I’d want it to be consumed by compiler plugins too.
End of conversation
New conversation -
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.