-
Notifications
You must be signed in to change notification settings - Fork 599
Removed @clockworklabs/typescript-sdk
in favor of spacetimedb
#3262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
7737f3f
to
a83cd9a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, this LGTM for the level of review I'm willing to do right now. It sounds like our plan is to test tomorrow morning.
…bs/typescript-sdk` in favor of `spacetimedb`
To be clear I have tested this release, but would like to do additional testing once we've published the package with the latest version to ensure it's working on npm. |
Description of Changes
This PR removes the
@clockworklabs/typescript-sdk
from the repository and retains onlyspacetimedb
in thecrates/bindings-typescript
directory. Some files are migrated tospacetimedb
. I have also updated the appropriate READMEs.In addition I have symlinked the old
sdks/typescript
directory to point tocrates/bindings-typescript
.API and ABI breaking changes
This is not technically a breaking change of any kind, although it does orphan and deprecate the @clockworklabs/spacetimedb-sdk npm package. This package will no longer work with SpacetimeDB.
Users should now install and use the
spacetimedb
package.Expected complexity level and risk
2, it's a straightforward change but affects many files.
Testing
pnpm test
in thespacetimedb
package