Forward-looking plans only — not a mirror of src/. Doc index: README.md. Design / ship: architecture.md, packaging.md. Shipped features (adapters, fixtures, codemap agents init — agents.md) live in src/ and linked docs — not enumerated here.
- Community language adapters — optional packages (e.g. Tree-sitter) with a peerDependency on
@stainless-code/codemapand a public registration API beyond built-ins insrc/adapters/. - Agent tooling — evaluate TanStack Intent for versioned skills in
node_modules(optional;codemap agents initremains the default). - Golden queries — design & policy: golden-queries.md; Tier A in CI, Tier B via
CODEMAP_*(see benchmark § Fixtures).
| Layer | Role |
|---|---|
| Core | Schema, incremental indexing, git invalidation, dependencies, CLI, query |
| Community adapters | Future optional packages; peerDependency on @stainless-code/codemap |
- Full-text search across all file bodies (use ripgrep / IDE)
- Replacing LSP or language servers
-
--performanceCLI flag — per-phase timing breakdown (glob, parse, resolve, insert, indexes) viaperformance.now();index-engine.tsalready has total elapsed, gap is per-phase granularity - Adapter scaffolding —
codemap create-adapter --name [name]generates adapter + test + fixture boilerplate; blocked on community adapter registration API (could land with manual registration) - Config loader — two candidates: (a) c12 — battle-tested (Nuxt/Nitro), adds extends, env overrides, RC files, watching; still executes config via
jiti. (b) AST-based extraction withoxc-parser— faster, no side effects, safer in untrusted repos; can't handle async/dynamic configs, needsimport()fallback. Current: nativeimport()inconfig.ts - MCP server wrapping
query - Watch mode for dev —
node:fs.watchrecursive +--filesre-index loop; Linuxrecursiverequires Node 19.1+ - Monorepo / workspace awareness — discover workspaces from
pnpm-workspace.yaml/package.jsonand index per-workspace dependency graphs - Optional GitHub Actions
workflow_dispatch— run golden/benchmark against a public corpus only (never private app code) - Optional FTS5 for opt-in full-text
- Sass / Less / SCSS: Lightning CSS is CSS-only; preprocessors need a compile step before CSS parsing — see architecture.md § CSS
- UnJS adoption — candidates:
citty(CLI builder),pathe(cross-platform paths),consola(structured logging),pkg-types(typedpackage.json/tsconfig.json),c12(config loader — see config loader item above)