I wish tsconfig.json could also be put inside of package.json, developers seem to love collecting special root files
-
Show this thread
-
Replying to @sebmck @sseraphini
also why are the by default in root can't there be a "configDirectory" in package.json
1 reply 0 retweets 17 likes -
yes! Who evem started this. Why do we not have a .config/ convention
2 replies 0 retweets 26 likes -
Replying to @kall @andreasklinger and
I feel like >80% of JS devs agree that there should be a ./config directory and yet it never happens.
1 reply 0 retweets 4 likes -
Replying to @jamonholmgren @andreasklinger and
if cosmiconfig would search in some folder by default it would be a big step. I don‘t know if they are open to it, since they implement convention and, well, I don‘t think there‘s any convention here.
1 reply 0 retweets 2 likes -
Replying to @kall @jamonholmgren and
someone has to be the change. Maybe if some new tool supported only that?
1 reply 0 retweets 4 likes -
-
Replying to @jamonholmgren @kall and
Valid config locations are package.json#rome rome.json rome.rjson .config/rome.json .config/rome.rjson
2 replies 0 retweets 10 likes -
Replying to @sebmck @jamonholmgren and
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..
1 reply 0 retweets 3 likes
~/.config is a convention already for a lot of tools
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 
