SebastianVerified account

I understand that it's a challenge, but personally I've found it to be a real pain to build an opinionated tool with little-to-no config (similar to react-scripts) on top of tool that doesn't support dynamic configuration.

If I generate the toml file, then I as the user of Rome would have to worry about cache invalidation/config regeneration. I suppose that's the trade-off that's being made. It's understandable that you'd prefer to keep it simpler for the more common case

What sort of configuration would you want to generate?

For babel, kcd-scripts adds the react preset if the host project's package.json includes a dependency on react. Does similar for eslint. For jest, it adds setupFilesAfterEnv if the host project has a file under tests/setup-env.js Stuff like that.

Those examples aren't super compelling since Rome will have the functionality of all those tools listed

I can't even tell you how excited I am for an advancement in JS tooling that'll eliminate the need for all these app scaffolding frameworks, boilerplates, etc etc etc. No pressure! :)

If a tool gets in the way of me fixing a build issue, I'll never use it. Too many edge cases. Set my defaults and hand me a webpack merge to ruin things for myself, or not.