Skip to content

Deprecate @sigmacomputing/plugin in favor of @sigmacomputing/plugin-sdk#60

Draft
Pearce-Ropion wants to merge 4 commits into
mainfrom
claude/zen-tesla-LZ6x4
Draft

Deprecate @sigmacomputing/plugin in favor of @sigmacomputing/plugin-sdk#60
Pearce-Ropion wants to merge 4 commits into
mainfrom
claude/zen-tesla-LZ6x4

Conversation

@Pearce-Ropion
Copy link
Copy Markdown
Collaborator

Summary

  • Renames the existing package in packages/plugin-sdk from @sigmacomputing/plugin to @sigmacomputing/plugin-sdk.
  • Adds a new packages/plugin workspace that keeps the @sigmacomputing/plugin name as a thin compatibility shim.
  • The shim depends on @sigmacomputing/plugin-sdk via workspace:^, re-exports its full public API (export * from '@sigmacomputing/plugin-sdk'), and emits a console.warn at import time directing consumers to migrate.
  • New packages/plugin/README.md clearly marks the package as deprecated and walks through migration.

Notes

  • The shim only emits ESM and CJS bundles (no UMD). UMD was dropped here because the deprecated package would otherwise have to inline all of @sigmacomputing/plugin-sdk into a UMD bundle, which is undesirable for a transitional shim. CDN/UMD users should migrate to @sigmacomputing/plugin-sdk.
  • The workspace:^ dependency on @sigmacomputing/plugin-sdk will be rewritten by yarn at publish time to ^<version>.
  • Existing top-level README.md / CHANGELOG.md / CONTRIBUTING.md references to @sigmacomputing/plugin were intentionally left as-is — happy to update those in a follow-up if desired.

Test plan

  • yarn install resolves the new workspace package
  • yarn build produces dist/{esm,cjs} for both packages
  • yarn types passes
  • yarn test passes (the shim has no tests; plugin-sdk tests run unchanged)
  • Import @sigmacomputing/plugin in a sample project and confirm the deprecation console.warn fires and all named exports still resolve

Generated by Claude Code

claude added 4 commits May 22, 2026 00:08
Rename the existing package in packages/plugin-sdk to
@sigmacomputing/plugin-sdk, and add a new packages/plugin workspace that
keeps the @sigmacomputing/plugin name as a thin compatibility shim. The
shim depends on @sigmacomputing/plugin-sdk, re-exports its entire public
API, and emits a console.warn at import time directing consumers to
migrate.
Replace the workspace:^ dependency on @sigmacomputing/plugin-sdk in the
deprecated shim with an explicit ^X.Y.Z range, since the workspace
protocol is not being rewritten to a concrete version at publish time.
Update the bump-version script to keep any @sigmacomputing/* dependency
in lockstep with the package version so the two stay in sync on every
release bump.
Mirror the plugin-sdk's tsdown.config.ts pattern by merging the
repository's shared base config. This restores the UMD bundle (which the
base config emits alongside ESM and CJS), so add unpkg and jsdelivr
entries back to the shim's package.json to advertise the UMD build.
bump-version.ts keeps every workspace package's version in lockstep
with the root, so the per-package __VERSION__ overrides duplicated the
root value. Inject __VERSION__ from the root package.json in
tsdown.base.ts (already there) and vitest.base.ts (added), and collapse
each package's tsdown.config.ts and vitest.config.ts into thin
pass-throughs of the base.
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.

2 participants