bundle-analyzable-paths — Claude Code rule: paths and install
The bundle-analyzable-paths rule recommends making import and file paths statically analyzable. That keeps bundlers from treating a broad set of files as reachable.
MIT ★ 1,216 updated 2026-10-24
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install react-skills@claude-settingsWhat bundle-analyzable-paths does
The rule covers dynamic imports and file-system access. For imports, it recommends mapping each allowed module to a function with a literal path. For file paths, use a literal final path in each conditional branch. The bundler can then see which files the code may reach.
In Next.js server code, passing a variable to path.join(process.cwd(), someVar) can broaden output tracing. A wider analysis can mean a larger server bundle, slower builds, longer cold starts, or more memory use. This matters because Next.js traces usage of import, require, and fs.
To add the rule to Claude Code, use the marketplace commands and then add the rule file. Note that the install command names react-skills@claude-settings, while the rule file is bundle-analyzable-paths.md.
What it helps with
- limit dynamic imports to an explicit module map
- use literal paths for content directories
- avoid broadening Next.js output tracing with a variable path
- narrow the files a bundler treats as reachable
Example prompts for the agent
- Rewrite page selection as a map of explicit dynamic imports.
- Replace the variable content path with literal paths in each branch.
- Review this Next.js server code and narrow its file tracing.
How to install bundle-analyzable-paths
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install react-skills@claude-settings2Manually: put the files in place
.claude/rules/bundle-analyzable-paths.mdThe paths frontmatter field limits the files
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.cursor/rules/bundle-analyzable-paths.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.github/instructions/bundle-analyzable-paths.instructions.mdThe applyTo field sets which files it applies to
Manually: put the files in place
.devin/rules/bundle-analyzable-paths.mdManually: put the files in place
.clinerules/bundle-analyzable-paths.mdStep by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use
Questions about bundle-analyzable-paths
How do I install bundle-analyzable-paths in Claude Code?
Run these steps in order: /plugin marketplace add fcakyon/claude-codex-settings, then /plugin install react-skills@claude-settings, then add .claude/rules/bundle-analyzable-paths.md.
What does bundle-analyzable-paths do?
It advises writing import and file-system paths so build tools can determine reachable files during the build. For dynamic imports, it recommends an explicit map of allowed modules.
Why does the rule mention Next.js output tracing?
In server code, path.join(process.cwd(), someVar) can expand the traced file set. Next.js analyzes import, require, and fs usage.
Source text
bundle-analyzable-paths.md · MIT
---
title: Prefer Statically Analyzable Paths
impact: HIGH
impactDescription: avoids accidental broad bundles and file traces
tags: bundle, nextjs, vite, webpack, rollup, esbuild, path
---
## Prefer Statically Analyzable Paths
Build tools work best when import and file-system paths are obvious at build time. If you hide the real path inside a variable or compose it too dynamically, the tool either has to include a broad set of possible files, warn that it cannot analyze the import, or widen file tracing to stay safe.
Prefer explicit maps or literal paths so the set of reachable files stays narrow and predictable. This is the same rule whether you are choosing modules with `import()` or reading files in server/build code.
When analysis becomes too broad, the cost is real:
- Larger server bundles
- Slower builds
- Worse cold starts
- More memory use
### Import Paths
**Incorrect (the bundler cannot tell what may be imported):**
```ts
const PAGE_MODULES = {
home: './pages/home',
settings: './pages/settings',
} as const
const Page = await import(PAGE_MODULES[pageName])
```
**Correct (use an explicit map of allowed modules):**
```ts
const PAGE_MODULES = {
home: () => import('./pages/home'),
settings: () => import('./pages/settings'),
} as const
const Page = await PAGE_MODULES[pageName]()
```
### File-System Paths
**Incorrect (a 2-value enum still hides the final path from static analysis):**
```ts
const baseDir = path.join(process.cwd(), 'content/' + contentKind)
```
**Correct (make each final path literal at the callsite):**
```ts
const baseDir =
kind === ContentKind.Blog
? path.join(process.cwd(), 'content/blog')
: path.join(process.cwd(), 'content/docs')
```
In Next.js server code, this matters for output file tracing too. `path.join(process.cwd(), someVar)` can widen the traced file set because Next.js statically analyze `import`, `require`, and `fs` usage.
Reference: [Next.js output](https://nextjs.org/docs/app/api-reference/config/next-config-js/output), [Next.js dynamic imports](https://nextjs.org/learn/seo/dynamic-imports), [Vite features](https://vite.dev/guide/features.html), [esbuild API](https://esbuild.github.io/api/), [Rollup dynamic import vars](https://www.npmjs.com/package/@rollup/plugin-dynamic-import-vars), [Webpack dependency management](https://webpack.js.org/guides/dependency-management/)
© fcakyon · MIT · fcakyon/claude-codex-settings