Tree-sitter never loaded in a packaged install (#47)

[nedonatelli]

Closes #47.

The bug

const modulePath = './treeSitterAnalyzer.js';
const mod = await import(modulePath).catch(() => null);

The indirection existed to stop static resolution — its comment says the module
is "optional, it only exists when tree-sitter grammars are installed".
src/parsing/treeSitterAnalyzer.ts is tracked in git and always present, so that
premise was stale. What the indirection still did was stop esbuild bundling
it, leaving a runtime specifier pointing at a file dist/ does not contain.

.catch(() => null) sat inside the try block and absorbed exactly the error the
outer logger.warn existed to report. Silent, every time.

Confirmed three ways

static	dist/ and the VSIX contain no treeSitterAnalyzer.js — only extension.js and its map
runtime	reproducing the call site from dist/ → ERR_MODULE_NOT_FOUND
empirical	the graph 0.122.4 actually cached matches regex (6,541 symbols over src/), not tree-sitter (5,836)

What this means retroactively

The perDeclarator mapping that fixed 221 invisible exported constants, and the
generator_function_declaration mapping from #45, never ran in production.
Both happened to have regex counterparts doing the real work — luck, not design.

The extension shipped 28 MB of .wasm grammars it could not load, and parsed
everything with the less precise fallback (regex yields ~13% more symbols on the
same tree; that gap is false positives, not coverage).

The fix

Literal specifier, so esbuild bundles the module. Grammar loading stays lazy —
the expensive work is inside createTreeSitterAnalyzer, not the import. The
swallow is gone and the fallback now names what degrades.

The test reads the build output

Every existing test in src/parsing/ calls createTreeSitterAnalyzer directly
and passed throughout — they verify a path no install reached. That is the
sharpest form of this repo's recurring failure: not a check that measures
nothing, but one that measures something real which users never execute.

The new suite asserts on dist/extension.js: the analyzer is present, no
dist-relative runtime import survives, and the failure path is not silent. It
throws in CI if the bundle is missing, mirroring grammarsTestSupport — a
skipped suite here would cover nothing while reporting green.

Mutation-checked: restoring the old load path and rebuilding fails two of three.

Verified in a real package

generator_function_declaration     1
createTreeSitterAnalyzer           2
Tree-sitter failed to load         1
dangling ./ runtime import         0

npm run check: 8622 passed, 2 skipped, 465 files. Integration: 45 passing.

🤖 Generated with Claude Code

[github-actions]

✅ All checks passed

Check	Status
Type check	✅ success
Lint	✅ success
Tests	✅ success

Posted by SideCarAI-Bot