thirdweb JavaScript/TypeScript monorepo
Best in class web3 SDKs for Browser, Node and Mobile apps
## Packages
| Package | Description | Latest Version |
| ---------------------------------------- | -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [/sdk](./packages/sdk/README.md) | Best in class web3 SDK for Browser, Node and Mobile apps |
|
| [/react](./packages/react/README.md) | Ultimate collection of React hooks for your web3 apps |
|
| [/auth](./packages/auth/README.md) | Best in class wallet authentication for Node backends |
|
| [/storage](./packages/storage/README.md) | Best in class decentralized storage SDK for Browser and Node |
|
| [/cli](./packages/cli/README.md) | Publish and deploy smart contracts without dealing with private keys |
|
| [/solana](./packages/solana/README.md) | Solana SDK for Browser, Node and React Native |
|
## How this monorepo functions
### Contributing
1. Create PRs to the monorepo
2. 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)
3. Create a `changeset` (with `yarn changeset`) for every **user impacting** change and describe what changed (try to focus on the end-user impact as much as possible -- use `major` for breaking changes, `minor` for new features, `patch` for non-breaking bug fixes, etc)
4. when the PR builds and tests pass merge to main
### Releases
#### Nightly
- every push to main automatically gets published to the `@nightly` tag as a snapshot version (based on the commit hash)
- nightly versions are published to npm under the `@nightly` tag
#### Stable
- every push to main that contains a changeset automatically gets added to the [Version Packages](https://github.com/thirdweb-dev/js/tree/changeset-release/main) 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 Packages` PR to main, this will automatically create new `@latest` packages for all of the packages in the monorepo that have changesets