he/him 
Rome config option names
Show this thread
-
`rome.config.ts` Seemingly a weird choice, but my reasoning is that it's very nice for configuration files to be 'typed'.
Having dynamic configuration makes it extremely hard (or impossible) to derive cache keys. I don't think there's any part of the Rome configuration that would benefit from being constructed that way. You can also construct TOML configs yourself if you want.
-
-
Will TOML autocomplete? I don't like to have to constantly check the docs to remember the names of properties. Also, unsure what you mean by dynamic configuration.
-
In order to know what the configuration is, you have to execute the script, it can do literally anything. No idea about autocomplete but VS Code has it for JSON so don't see why it couldn't have it for TOML.
- 1 more reply
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.