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.

Fallow ships with 94 built-in plugins for the most 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.
PluginEnabler packages
Next.jsnext
Nuxtnuxt, nuxt3
Remix@remix-run/dev
SvelteKit@sveltejs/kit
Gatsbygatsby
Astroastro
Angular@angular/core
React Routerreact-router, @react-router/dev
TanStack Router@tanstack/react-router, @tanstack/start, @tanstack/react-start
React Nativereact-native
Expoexpo
NestJS@nestjs/core
Docusaurus@docusaurus/core
Nitronitropack
Capacitor@capacitor/core, @capacitor/cli
Sanitysanity, @sanity/
VitePressvitepress
next-intlnext-intl
Relayrelay-runtime, react-relay, relay-compiler
Electronelectron, electron-builder, @electron-forge/cli, electron-vite
Qwik@builder.io/qwik, @builder.io/qwik-city, @qwik.dev/core, @qwik.dev/router
i18nexti18next, react-i18next, vue-i18n
Convexconvex
Litlit, lit-element, lit-html (also activates for native Custom Elements without a Lit dependency)
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:
PluginWhat it extracts
ESLintPlugin imports, shared configs, custom rule paths, import resolver packages
VitestReporters, coverage provider, typecheck checker, browser provider from vitest.config.ts
ViteEntry points, resolve.alias mappings, plugin imports from vite.config.ts
JestSetup files, transform paths, module mappers from jest.config.js
tsdDeclaration test directory from package.json#tsd.directory
StorybookStory globs, addon imports from .storybook/main.ts
TailwindContent paths, plugin imports from tailwind.config.js
WebpackEntry points including descriptor/context forms, resolve.alias mappings, loader/plugin imports from webpack.config.js
TypeScriptPath aliases, project references from tsconfig.json
BabelPlugin and preset imports from babel.config.js
RollupEntry points, plugin imports from rollup.config.js
RolldownEntry points, external deps, plugin imports from rolldown.config.ts
PostCSSPlugin imports from postcss.config.js
NuxtModules, plugins, server routes, alias, imports.dirs, components, srcDir from nuxt.config.ts
SvelteKitkit.alias mappings, param matchers from svelte.config.js
Next.jsApp Router convention exports (page, layout, loading, error, route), route segment config, Pages Router exports, middleware, proxy, instrumentation, mdx-components, transpilePackages
RsbuildEntry points, plugin imports from rsbuild.config.ts
RemarkPlugin imports from .remarkrc.js
AngularStyles, scripts, main, polyfills from angular.json build targets; @Component({ templateUrl, styleUrl }) decorator references create graph edges; standalone .html templates and inline template: literals both contribute synthetic <template> complexity findings (@if/@for/@switch/@defer, *ngIf, bound attributes, interpolations) suppressible via <!-- fallow-ignore-file complexity --> (external) or // fallow-ignore-next-line complexity above the @Component decorator (inline)
NxExecutor references, main entry points, tsconfig paths from project.json
HardhatPlugin imports and side-effect requires from hardhat.config.ts
UnoCSSPreset and transformer imports from uno.config.ts
Run fallow list --plugins to see which plugins are active in your project.
$ fallow list --plugins
Active plugins:
  - nextjs
  - vite
  - vitest
  - playwright
  - storybook
  - eslint
  - typescript
  - tailwind
  - drizzle
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.