Where Does Taplo Store Its Config?
Taplo reads .taplo.toml (then taplo.toml) in the working dir, overridable with --config or TAPLO_CONFIG.
Last updated
Taplo looks for .taplo.toml first, taplo.toml second, in the working directory or workspace root. The file sets include/exclude globs, formatter rules and the JSON schema used for validation.
An empty include list means no files at all, which bites everyone once. Omit include to cover the whole tree, then carve out with exclude, and pin per-file schemas with header directives where the global one lies.
Where Taplo stores this, by platform
[RepoDir]\.taplo.toml
Globs, formatter rules, schema path. Editor plugins and LSP servers read the same file, so CLI and IDE stay in sync automatically.
[RepoDir]/.taplo.toml
Same discovery order. Directives (#:schema) inside individual files override the configured schema per document.
[RepoDir]/.taplo.toml
Same layout. RUST_LOG=error taplo lint quiets the chatty default logging when the config itself is what you are debugging.
Frequently asked questions
How do I point Taplo at a config elsewhere?
Pass --config <path> (wins over everything) or set TAPLO_CONFIG. --no-auto-config disables discovery entirely, which suits editor integrations with their own settings.
Can one TOML file use a different schema than the project default?
Yes, with #:schema directives at the top of the file. A relative path or URL there beats the config file schema for that document only.
Notice an outdated path? Let us know.