Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.fallow.tools/llms.txt

Use this file to discover all available pages before exploring further.

Print the resolved configuration and the path of the config file that was loaded. Useful for debugging “why isn’t my config being applied?” especially in monorepos where multiple .fallowrc.json files may be in play. 
fallow config
By default, prints the loaded config path on the first line followed by the JSON-serialized config (with extends resolved):
$ fallow config
loaded config: /repo/.fallowrc.json
{
  "entry": ["src/main.ts"],
  "ignorePatterns": ["dist/**"],
  "duplicates": {
    "ignoreImports": true
  },
  ...
}

​
Options

FlagDescription
--pathPrint only the config file path, one line, no JSON. Easier to consume from shell scripts.
The global --config <path> flag is honored: if you pass it, that path is loaded directly instead of walking the directory tree.

​
Exit codes

CodeMeaning
0A config file was found and loaded
2Error (failed to parse, explicit --config path missing, etc.)
3No config file was found; defaults are in effect

​
Examples

​
Verify which config the LSP/CLI picked up

In a monorepo, when running fallow from inside a sub-package: 
cd packages/app
fallow config --path
# /repo/.fallowrc.json   (root config inherited — sub-package has none of its own)
If a sub-package has its own config, that path is printed instead (first-match-wins).

​
Use an explicit config file

fallow --config ./my-config.json config

​
Pipe to jq for further inspection

fallow config | tail -n +2 | jq '.duplicates'
The first line (loaded config: ...) is on stdout above the JSON, so tail -n +2 skips it.

​
Detect “no config” in scripts

if ! fallow config --path > /tmp/fallow-cfg-path 2>/dev/null; then
  echo "no fallow config found, will use defaults"
fi