Merged
Conversation
Drop the private flag so community connector authors can pull the SDK types/runtime directly instead of shimming it via file: or tarball. Add publishConfig, repository, license, keywords, and a prepack hook so `pnpm publish` produces a clean tarball (tests already excluded via tsconfig; dist-only files list unchanged). 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
"private": truefrom@spool/connector-sdkso community connector authors can install the SDK via npm instead of using file paths or tarballspublishConfig.access: public,repository,license,keywords,prepackhook~/.spool/connectors/node_modules/@spool/connector-sdkat runtime)Why now
P2 work on community plugin validation — currently external authors have no clean way to declare a dev-time dependency on the SDK. Publishing unblocks real community plugin development and lets us actually exercise the
spool://connector/install/trust flow with a non-@spool-lab/*plugin.Packaging verification
pnpm packproduces a tarball with onlydist/,README.md, andpackage.json(no tests — tsconfig excludes*.test.ts)vitestpasses (12/12)After merge
pnpm --filter @spool/connector-sdk publish --access publicunder the spool-lab npm orgTest plan
pnpm --filter @spool/connector-sdk buildpassespnpm --filter @spool/connector-sdk testpassespnpm packtarball contents verified (no src, no tests)pnpm publish --dry-runclean🤖 Generated with Claude Code