Describe what you want

Hello! there's a new convention proposal about how we handle config files across our projects. As someone who loves using Drizzle, I'd love this to happen so we can keep all the config files from different tools in one place.

The proposal suggests adding support for .config/drizzle.ts, .config/drizzle.js, and .config/drizzle.json as an alternative place to check and load Drizzle configurations if the traditional drizzle.config.ts file isn't present at the root level. This opens up the possibility of seamlessly transitioning to this fresh convention throughout our ecosystem.

See:

• .config dir proposal for more context
• https://twitter.com/_pi0_/status/1757418709574939058
• Relevant discussions