Best in class web3 SDKs for Browser, Node and Mobile apps
| Package | Description | Latest Version |
|---|---|---|
| /sdk | Best in class web3 SDK for Browser, Node and Mobile apps | |
| /react | Ultimate collection of React hooks for your web3 apps | |
| /auth | Best in class wallet authentication for Node backends | |
| /storage | Best in class decentralized storage SDK for Browser and Node | |
| /cli | Publish and deploy smart contracts without dealing with private keys | |
| /solana | Solana SDK for Browser, Node and React Native |
- Create PRs to the monorepo
- Tag PRs with
[SDK],[REACT],[AUTH], etc to indicate the package that you are engaging with (TBD a better process for this / if it is necessary) - Create a
changeset(withyarn changeset) for every user impacting change and describe what changed (try to focus on the end-user impact as much as possible -- usemajorfor breaking changes,minorfor new features,patchfor non-breaking bug fixes, etc) - when the PR builds and tests pass merge to main
- every push to main automatically gets published to the
@nightlytag as a snapshot version (based on the commit hash) - nightly versions are published to npm under the
@nightlytag
- every push to main that contains a changeset automatically gets added to the Version Packages PR
- to release a stable version of the code that is on main (with the change sets as the release notes / changelog) merge the
Version PackagesPR to main, this will automatically create new@latestpackages for all of the packages in the monorepo that have changesets