Skip to main content
Fallow ships with built-in plugins for popular TypeScript and JavaScript tools. Each plugin teaches fallow about framework-specific conventions: entry points, config files, used exports, and tooling dependencies. Analysis is accurate out of the box.
Most plugins activate automatically when the relevant package is in your package.json. Some plugins (ESLint, Vitest) also activate when a config file is present in the workspace root, even without the package. This covers monorepos where the tool is installed at the root but workspace packages have their own config files.
These plugins go beyond simple package detection. They parse your config files with Oxc’s AST parser to extract entry points, dependencies, aliases, and other settings automatically:
Run fallow list --plugins to see which plugins are active in your project.
$ fallow list --plugins
Don’t see your framework? Custom plugins support any internal or third-party tool using declarative JSON or TOML.

See also

Custom plugins

Add support for internal frameworks with external plugin files.

fallow list

Inspect active plugins, entry points, and project metadata.