Skip to main content
Production mode restricts analysis to code that ships to users, ignoring test and development files. 
fallow check --production
Or set it in your config: 
// .fallowrc.json
{
  "production": true
}

​
What changes in production mode

BehaviorDefaultProduction
Test files (*.test.*, *.spec.*, __tests__/)IncludedExcluded
Story files (*.stories.*)IncludedExcluded
Mock files (__mocks__/)IncludedExcluded
Package.json scripts analyzedAllOnly start, build, serve, preview, prepare
Unused devDependenciesReportedSkipped
Type-only dependenciesNot flaggedFlagged (should be devDependencies)
$ fallow check --production
Production mode: excluding test/dev files, analyzing start/build scripts only

Unused exports (2)
  src/utils/format.ts
    :12 formatCurrency
    :28 formatPercentage

Unused dependencies (1)
  moment

Type-only dependencies (1)
  zod  →  should be a devDependency (only imported via 'import type')

Found 4 issues in 19ms (production mode, 623/847 files analyzed)

​
Type-only dependency detection

In production mode, fallow detects dependencies that are only imported via import type: 
import type { Config } from 'some-package';  // Type-only — erased at runtime
These packages should be devDependencies since types are erased at runtime and don’t need to be installed in production.
In monorepos, production mode catches dependencies that should be devDependencies, keeping each package’s install footprint minimal.

​
See also

CI Integration

Use production mode in your CI pipeline for lean, fast checks.

Rules & Severity

Control which issue types are errors, warnings, or disabled.