I wish tsconfig.json could also be put inside of package.json, developers seem to love collecting special root files
-
-
A single location would be fine but people will complain why they need a .config folder that none of their other tools use. It’s very low effort to support multiple possible locations to cover many uses. Rome will also correctly save to all of them (including package.json)...
-
If the config needs to be modified by a command
End of conversation
New conversation -
-
-
Any particular reason for .config/ over config/? The . complicates some tooling, like being ignored by default by eslint, although that example obviously doesn’t matter if using Rome..
-
~/.config is a convention already for a lot of tools
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.
he/him 
