fix(engine): pin web-tree-sitter back to ^0.20.8, unblocking the engine build - #9234
Merged
Conversation
…ne build The dependency bump in #9232 jumped web-tree-sitter 0.20.8 -> 0.26.11, a breaking major-version range change: Parser.init() and the SyntaxNode export moved, breaking src/miner/repo-map.ts's tsc build for every PR based on main since that merge.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
2 tasks
JSONbored
added a commit
that referenced
this pull request
Jul 27, 2026
…endencies (#9242) test/unit/repo-map.test.ts imports both directly from the repo root, but they were only declared under packages/loopover-engine/package.json. Pinning web-tree-sitter back to ^0.20.8 (#9234) changed npm's hoisting decision and left both packages nested under packages/loopover-engine/node_modules/ only, breaking that root-level test's module resolution in CI. Declaring them as root devDependencies (matching the engine's pinned version) makes them resolvable from root-level tests regardless of hoisting.
7 tasks
This was referenced Jul 30, 2026
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.
Summary
The npm dependency bump in #9232 jumped
web-tree-sitterfrom^0.20.8to^0.26.11— a breaking major-version range change.Parser.init()and theSyntaxNodeexport moved in the new major version, breakingpackages/loopover-engine/src/miner/repo-map.ts'stscbuild. This has been failing the engine build (and any CI job that builds it) for every PR based onmainsince that merge — confirmed reproducing on a freshorigin/maincheckout.This PR pins
web-tree-sitterback to^0.20.8(the previously-working range) rather than migratingrepo-map.tsto the new major-version API, to unblock CI immediately. A proper migration to 0.26.x (updatingrepo-map.tsfor the newParser.init()/SyntaxNodeshape) can follow as a separate, deliberate PR.Test plan
npm run build --workspace @loopover/engine— clean (was failing before this pin)npx tsc --noEmit -p tsconfig.json --incremental false— clean across the whole repo