chore: rename @spool/connector-sdk to @spool-lab/connector-sdk#89
Merged
chore: rename @spool/connector-sdk to @spool-lab/connector-sdk#89
Conversation
The SDK needs to be published to npm so community authors can depend on it. npm scope names map 1:1 to org or user names, and graydawnc owns @spool-lab on npm (not @spool). Renaming to @spool-lab/connector-sdk aligns the SDK scope with the org that actually publishes it. Mechanical changes: - Package name flip + all import-path updates across core, connectors, dev-connectors symlink, docs, workflow, bundle/phantom scripts - Bump patch version on all @spool-lab/connector-* packages that are already on npm (reddit, hackernews-hot, typeless, xiaohongshu → 0.1.1; github → 0.1.2) so republishing picks up the renamed peerDep - bundle-extract reads package name from the tarball manifest, so no hardcoded SDK path changes are needed there Runtime impact: existing user installs of @spool-lab/connector-*@0.1.0 import from @spool/connector-sdk, which will no longer exist after the Spool app is rebuilt from this main. They need to upgrade the installed connector packages to pick up the renamed imports — the update checker shipped in #66 handles this automatically on next app launch. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
@spoolscope is reserved on npm and not owned by the publishing account; aligning the SDK's scope with@spool-lab(where all official connectors already live) unblocks publishing@spool-lab/connector-*packages so they can be rebuilt with the renamed peerDepWhy
Follow-up to #88 — publishing the SDK failed with a 404 because
graydawncisn't an admin of the@spoolscope and npm won't let us register it (reserved). Keeping the SDK internal defeats the purpose of #88.@spool-lab/connector-sdkmatches the scope that already owns all the official connector packages on npm, keeps everything under one org, and matches the GitHub org.Changes
@spool/connector-sdk→@spool-lab/connector-sdkeverywhere (package name, all imports, devDeps/peerDeps, dev-connectors symlink scope path, bundle/phantom scripts, docs, workflow)@spool/core,@spool/app,@spool/cli,@spool/landing) are untouched — they are not publishedRuntime impact
Existing installs of
@spool-lab/connector-*@0.1.0import from the old SDK path and will break after a user upgrades Spool. The update checker from #66 picks up the bumped versions on next launch and re-installs them with corrected imports.Test plan
pnpm -r build(SDK + all connectors + core + cli) cleanpnpm --filter @spool/app exec tsc --noEmitclean@spool-lab/connector-sdk@0.1.0to npm🤖 Generated with Claude Code