Tools: Project config file - minimize API

[adrianhasna]

One of the project goals is to minimize the API, but right in the getting started guide, we see the project configuration "can take three possible forms": rome.json, rome.rjson or "rome" entry in package.json.
Already too many options. Is there a case where a project won't have a package.json!?

IMHO we should stick to "rome" entry in package.json.

[eddiemonge]

package.json can and already is already pretty crowded. Minimizing the API to me does not mean limiting the choices in how to do configuration, but in having less configuration.

[sebmck]

Already too many options. Is there a case where a project won't have a package.json!?

Yes. You can have subprojects with different settings. package.json also doesn't allow comments which is one of the greatest advantages of RJSON #13.

[talentlessguy]

I don't think this is a good idea because a lot of people are used to config files instead of putting everything to package.json

importing either json from the config or package.json won't make a huge difference. Both can be supported, it won't lose much in performance (as I think)

[sebmck]

Also in favor of removing package.json and having only rome in package.json and rome.rjson.

[milesj]

Please no config in package.json, it's the most restrictive format. Hell, even JSON is an awful config format.

[sebmck]

@milesj Hence RJSON #13. I don't see a problem with allowing people to put it in there if they want, especially if the config is only very small.

[Janne252]

I think I would prefer having support for *.js / *.ts configuration file as some options might be useful to resolve at runtime, like checking custom command line arguments. Some tools even have support for a default exported async function that resolves the configuration.