In our repo we have a file called dprint.jsonc that is NOT a dprint config file. Long story short this is how we configure our binary distribution for dprint.

Recently some infra constraints have been lifted internally which means we no longer need to pass plugins to dprint via CLI flags. This has revealed a problem.

When we run dprint fmt, dprint will crawl the entire repo looking for /dprint.jsonc?/ files. Dprint then finds the aforementioned not-dprint-config-file, loads it and then barfs:

No formatting plugins found. Ensure at least one is specified in the 'plugins' array of the configuration file.

Previously this error was hidden because we passed --plugins via CLI and so it override the lack of a plugins array.

I have tried to work around this by using the --config CLI arg -- but this doesn't disable dprint's config file search logic so it still finds the not-config file and errors.

So the request is one of:

• provide a way to ignore a specific file / not treat it as a config
• provide a way to ONLY respect one config file in the repo and ignore all others

The latter would probably be preferable TBH because we expect that each repo has exactly 1 config file in the monorepo root.