refactor(deps): ai-kit comes from npm — @bitbaum/ai-kit ^0.6.2 - #473
Merged
Conversation
The package is now published to the npm registry as @bitbaum/ai-kit (npm's typosquat guard blocked the bare name "ai-kit", hence the scope; ai-kit PR #25 documents the rename — content is identical to the github:bitbaum/ai-kit#v0.6.2 tag). The git pin is retired: the lockfile no longer records the writer's ssh transport and npm-major-specific resolution for this dependency, so the whole lockfile-writer trap class dies with it. All imports move from 'ai-kit' / 'ai-kit/grounding' to '@bitbaum/ai-kit' / '@bitbaum/ai-kit/grounding'. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WqKqMnHQHSmkGFfc5t7Rxn
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.
What
Swaps the
ai-kitdependency from the git pin (github:bitbaum/ai-kit#v0.6.2) to the freshly published npm package@bitbaum/ai-kit@^0.6.2, renaming every import path:ai-kit→@bitbaum/ai-kitandai-kit/grounding→@bitbaum/ai-kit/grounding.Why the scope
npm's typosquat guard blocked publishing the bare name
ai-kit, so the package ships scoped as@bitbaum/ai-kit(documented in ai-kit PR #25, now merged — the npm tarball is content-identical to thev0.6.2git tag apart from the package name).Why retire the git pin
Git pins made the lockfile record the writer's transport and npm-major-specific resolution for this dependency — the lockfile-writer trap class that has bitten this fleet repeatedly (this repo's own
sweep-gh-owner.shheader documents the day an owner rename broke every install). With a registry dependency that class dies entirely.Changes
package.json:"ai-kit": "github:bitbaum/ai-kit#v0.6.2"→"@bitbaum/ai-kit": "^0.6.2"(samedependenciessection)src/lib/agent/*,src/lib/loki-core.ts,src/lib/ai/health.ts,src/lib/ai-budget/fair-share.ts,src/lib/agent/groq-error.ts,src/config/chat-models.ts, andscripts/test/*(root and/groundingsubpath imports).husky/pre-push"Cannot find module" note)scripts/test/agent-name-lookup.ts("the moment the chain moved intoai-kit") andscripts/ci/sweep-gh-owner.sh(describes the pastgithub:failure mode)node_modules/ai-kitorgithub:entry remainsVerification
npm run lint— 0 errorsnpx tsc --noEmit— cleannpm run test:unit— 130/130 unit test files passed (grounding suites included, now against the npm package)🤖 Generated with Claude Code
https://claude.ai/code/session_01WqKqMnHQHSmkGFfc5t7Rxn