Skip to content

deps: hold @types/better-sqlite3 at ^7 (fixes plain npm install after #42), list deployed plugins in .bb/plugins.json - #62

Merged
trotterdylan merged 1 commit into
mainfrom
bb/i-think-maybe-this-pr-broke-bb-because-of-the-sq-thr_23iz4wjdzz
Oct 22, 2026
Merged

trotterdylan merged 1 commit into
mainfrom
bb/i-think-maybe-this-pr-broke-bb-because-of-the-sq-thr_23iz4wjdzz

Conversation

@trotterdylan

Copy link
Copy Markdown
Collaborator

Ivy could not install thread-briefs from a checkout: npm install fails with an ERESOLVE peer conflict. #42 moved @types/better-sqlite3 to ^9.6.0 in ten plugins, but @get-bb/plugin-sdk (0.6.37, and every other version) declares an optional peer of ^7.6.12 on it. CI and the bb-server image install with --legacy-peer-deps, which is why neither noticed; the deployed servers are unaffected.

What this does

  • Puts @types/better-sqlite3 back to ^7.6.13 in devbox-provider, team-setup, repo-dashboard, github-watcher, linear, thread-briefs, multi-repo, slack, workstreams and stewards, and refreshes their lockfiles. The plugins import better-sqlite3 for its types only and get the database from the bb host (bb 0.46.0 itself runs better-sqlite3 13.0.3), so the ^7 typings lose nothing.
  • The lockfiles are regenerated with --legacy-peer-deps, as deps: npm group update (replaces #41), with the fixes it needed #42's were. A strict regeneration marks the SDK's optional peers (react, hono, better-sqlite3, testing-library, …) devOptional, which npm ci --omit=dev then installs: stewards' production install went from 9 packages to 38 that way. With the legacy flag it stays at 9.
  • dependabot.yml ignores @types/better-sqlite3, with a comment explaining the deliberate hold, so the next grouped update does not move it again. Move it when the SDK's peer range moves.
  • .bb/plugins.json gains the seven deployed plugins it was missing: thread-briefs, multi-repo, team-setup, linear, github-watcher, stewards and slack.

Verified

  • Plain npm ci (no legacy flag) now resolves in all ten plugins; before, thread-briefs failed with Conflicting peer dependency: @types/better-sqlite3@7.6.13.
  • npm ci --omit=dev --legacy-peer-deps: stewards 9 packages, linear 3, thread-briefs 1 (unchanged from main).
  • Typecheck and tests pass in stewards, linear, github-watcher and thread-briefs; the lockfile diffs touch only the @types/better-sqlite3 entries.

Lane: no-review (dependency range reverted to what the SDK requires; no runtime change).

Merging moves the bb-plugins pin, builds a new bb-server image and stages a restart on every developer's server.

🤖 Generated with Claude Code

— from bb thread thr_23iz4wjdzz

…n in .bb/plugins.json

#42 moved @types/better-sqlite3 to ^9.6.0 in ten plugins, but
@get-bb/plugin-sdk declares an optional peer of ^7.6.12 on it, so a
plain `npm install` in any of those plugins fails with an ERESOLVE peer
conflict. CI and the bb-server image install with --legacy-peer-deps and
never saw it; a developer installing a plugin from a checkout did.

The plugins import better-sqlite3 for its types only and get the
database from the bb host, so the ^7 typings lose nothing. This puts
the range back to ^7.6.13 and refreshes the lockfiles (regenerated with
--legacy-peer-deps, like #42's, so the SDK's optional peers stay marked
dev and `npm ci --omit=dev` keeps installing only runtime packages).
dependabot.yml now ignores the package, with a note on why, so the next
grouped update does not move it again.

.bb/plugins.json also gains the seven deployed plugins it was missing:
thread-briefs, multi-repo, team-setup, linear, github-watcher, stewards
and slack.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@trotterdylan
trotterdylan merged commit 9b0a129 into main Oct 22, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant