feat(analyzers): recognize NestJS projects#3
Open
aolin480 wants to merge 5 commits into
Open
Conversation
aolin480
force-pushed
the
bugfix/huggingface-fix
branch
from
July 5, 2026 15:46
acb7cba to
e1ba165
Compare
aolin480
force-pushed
the
feature/nestjs-analyzer
branch
2 times, most recently
from
July 5, 2026 17:07
74acd54 to
677bc98
Compare
aolin480
force-pushed
the
bugfix/huggingface-fix
branch
from
July 5, 2026 17:07
e1ba165 to
b51adeb
Compare
React 19 and Next 16 added framework signals that the analyzers were not classifying yet. Keep the analyzer surface current without touching core search or indexing behavior.
We work in NestJS code often enough that treating it as generic TypeScript loses useful context. Add a dedicated analyzer for controllers, modules, providers, routes, DI, and common Nest packages so backend code gets the same first-class treatment as React and Next.js.
aolin480
force-pushed
the
feature/nestjs-analyzer
branch
from
July 15, 2026 19:58
677bc98 to
d083c3a
Compare
Large repositories were silently limited to the first 5,000 searchable chunks. Let each configured project raise that safety limit while keeping 5,000 as the default for smaller codebases. Use the same setting in MCP server and CLI reindex paths so both keyword and semantic indexes cover the same files.
Keep the auto-extracted Git history in project memory so future searches can surface the fixes and test constraints already handled in this repository.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR currently includes files from the Hugging Face/reranker fix branch because it is stacked on top of
bugfix/huggingface-fix. The Hugging Face PR needs to be merged into the primary repository first: PatrickSys/codebase-context#125.Summary
Large repository indexing
While indexing a large Nx monorepo project, Codebase Context created more than 22,000 chunks but only kept the first 5,000 in both the semantic and keyword indexes. The limit was hardcoded in
CodebaseIndexer, so increasing chunk size would not fix the missing search coverage.This adds
projects[].parsing.maxChunksto~/.codebase-context/config.json:{ "projects": [ { "root": "/path/to/large-project", "parsing": { "maxChunks": 25000 } } ] }The default stays at 5,000 for smaller projects. A project can raise the limit when it has enough files to exceed that safety cap. The value is validated as a positive integer and is used by both indexing paths:
codebase-context reindexresolves the current root against the same server config.Verification
pnpm buildpnpm format:checkpnpm test— 624 tests passed across 87 filesmaxChunks: 25000Notes
bugfix/huggingface-fixand should be reviewed after the Hugging Face/reranker branch lands upstream.maxChunksincreases embedding time, memory use, and local index size. The override is intentionally per project rather than a larger global default.