Fix dual @intx/types identity so local typecheck matches CI - #448
Merged
TheGreatAxios merged 1 commit intoAug 10, 2026
Merged
Conversation
Bun overrides already point install-time resolution at vendor/intx-types, but a nested published @intx/types@0.2.2 under @intx/agent can still give tsc a second type identity (missing PendingOperation.kind and related shapes). Pin tsconfig paths at the vendor source so local typecheck matches CI regardless of that layout, and document both layers.
TheGreatAxios
added
bug
TheGreatAxios
deleted the
cl-5855-fix-dual-intxtypes-identity-so-local-typecheck-matches-ci
branch
August 10, 2026 02:14
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
1 participant
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
@intx/types/@intx/types/*in roottsconfig.jsonpaths tovendor/intx-typesso TypeScript always sees one identity.overrideshandle install/runtime resolution while paths are required fortscwhen a nested published@intx/types@0.2.2reappears under packages like@intx/agent.Fixes CL-5855.
Why
Clean
bun installalready links agent → vendor via workspace overrides. A stale or partial layout can still leave published@intx/types@0.2.2nested under@intx/agent, andtscthen treats vendorPendingOperation(haskind) and publishedPendingOperation(nokind) as incompatible types — local typecheck fails while CI (clean install) stays green.Approach
tsconfig paths + existing overrides (minimal durable fix):
Evidence
After clean install in this worktree:
node_modules/@intx/types→vendor/intx-typesnode_modules/.bun/@intx+agent@…/node_modules/@intx/types→vendor/intx-types@intx+types@0.2.2package slot under.bunbun run typecheckexit 0Forced dual filesystem layout (agent nested types = published cache copy):
PendingOperation.kind, directors, context stores, compactorsbun run typecheckexit 0Test plan
bun install→ single realpath for top-level and agent-nested@intx/types(vendor)bun run typecheckpasses on clean installbun run typecheckstill passes with forced nested published@intx/types@0.2.2under agent