Skip to content

chore: centralize esbuild version with pnpm catalog#659

Open
Shinyaigeek wants to merge 1 commit into
thesysdev:mainfrom
Shinyaigeek:chore/centralize-esbuild-catalog
Open

chore: centralize esbuild version with pnpm catalog#659
Shinyaigeek wants to merge 1 commit into
thesysdev:mainfrom
Shinyaigeek:chore/centralize-esbuild-catalog

Conversation

@Shinyaigeek

Copy link
Copy Markdown
Contributor

What

esbuild was pinned independently in two internal packages, drifting between minor patch versions:

  • packages/openui-cli^0.25.10 (dependencies)
  • packages/browser-bundle^0.25.12 (devDependencies)

This moves esbuild into the shared pnpm catalog: at ^0.25.12 (the higher of the two, so neither package downgrades) and switches both packages to reference catalog:.

Why

Follows the same pattern as the recently centralized @types/node (#653/#656) and the eslint/typescript tooling already in the catalog — one source of truth, bump in one place, no silent drift between packages.

Notes

  • openui-cli effectively moves 0.25.10 → 0.25.12, a patch within the same ^0.25 range — no behavior change.
  • Lockfile regenerated via pnpm install --lockfile-only.

🤖 Generated with Claude Code

esbuild was pinned independently in two internal packages
(openui-cli at ^0.25.10, browser-bundle at ^0.25.12). Move it into
the shared pnpm catalog at ^0.25.12 and reference it via catalog: so
both packages stay aligned and bump in one place.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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