he/him 
I haven't posted anything about Rome in a while so here is what I worked on this evening. These are more error messages. It's obviously not all I'm working on but it's the easiest thing to tweet and discuss.
Show this thread
-
Rome ingests package.json files and performs some normalization and validation. One of the fields is name. When you use a package.json name in npm or yarn that is invalid, it will just yell at you. Rome points to the exact location with some possible hints. Examples:
Show this thread
-
-
-
These errors aren't generated until after either. The validation logic actually does some rough "autofixing". It would be possible to have a flag that suppresses the errors and writes the normalized fixed version to disk. Super nuanced and hard UX though to implement.
Show this thread
End of conversation
New conversation -
-
-
Curious to see how you keep these organized and maintainable. It feels like a *lot* of highly specific code maybe?
-
Not really. You queue up errors, always recovering from them by normalizing input etc. Then you have a boundary where you either dump the errors and stop, or write the normalized values somewhere when there's a --fix flag. Easily abstracted.
- 5 more replies
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.