fallow: codebase intelligence for TypeScript and JavaScript

Print the resolved configuration and the path of the config file that was loaded. Useful for debugging “why isn’t my config being applied?” 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

Flag	Description
`--path`	Print 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

Code	Meaning
`0`	The default view succeeded: a config file was found and loaded, or, on a zero-config project, the effective defaults were printed
`2`	Error (failed to parse, explicit `--config` path missing, etc.)
`3`	`--path` mode only, when no config file exists (there is no path to report). The default view prints the defaults and exits `0` instead.

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 | jq '.duplicates'

The loaded config: ... disclosure goes to stderr, so stdout is the JSON document alone. See Loaded config disclosure.

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

Configuration overview: supported config file names and the full schema
Monorepo configuration: how config discovery works in workspaces

​Options

​Exit codes

​Examples

​Verify which config the LSP/CLI picked up

​Use an explicit config file

​Pipe to jq for further inspection

​Detect “no config” in scripts

​Related