This is a monorepo of Blocto JavaScript SDK. Check out the docs here: docs.blocto.app.

There are some adapters to make it easier to integrate:

lib name	npm
@blocto/aptos-wallet-adapter-plugin
@blocto/web3-react-connector
@blocto/wagmi-connector
@blocto/rainbowkit-connector
@blocto/web3modal-connector

This repo includes the following packages/apps:

• packages: shared packages
• adapters: adapters using Blocto JavaScript SDK
• eslint-config-custom: eslint configurations (includes eslint-config-next and eslint-config-prettier)
• tsconfig: tsconfig.jsons used throughout the monorepo

This Turborepo has some additional tools already setup for you:

• TypeScript for static type checking
• ESLint for code linting
• Prettier for code formatting

blocto-sdk
├─ packages
│  ├─ @blocto/sdk
│  │  └─ package.json
│  ├─ tsconfig
│  │  └─ package.json
│  └─ eslint-config-custom
│     └─ package.json
├─ adapters
│  ├─ @blocto/aptos-wallet-adapter-plugin
│  │  └─ package.json
│  ├─ @blocto/rainbowkit-connector
│  │  └─ package.json
│  └─ @blocto/wagmi-connector
│  │  └─ package.json
│  ├─ @blocto/web3-react-connector
│  │  └─ package.json
└─ package.json

To build all apps and packages, run the following command:

yarn build

Feel like contributing? That's awesome! We have a contributing guide to help guide you.

1. Run the command line script yarn changeset.
2. Select the packages you want to include in the changeset using ↑ and ↓ to navigate to packages, and space to select a package. Hit enter when all desired packages are selected.
3. You will be prompted to select a bump type for each selected package. Select an appropriate bump type for the changes made. See here for information on semver versioning
4. Your final prompt will be to provide a message to go alongside the changeset. This will be written into the changelog when the next release occurs. After this, a new changeset will be added which is a markdown file with YAML front matter.

-| .changeset/
-|-| UNIQUE_ID.md

The message you typed can be found in the markdown file. If you want to expand on it, you can write as much markdown as you want, which will all be added to the changelog on publish. If you want to add more packages or change the bump types of any packages, that's also fine.

While not every changeset is going to need a huge amount of detail, a good idea of what should be in a changeset is:

• WHAT the change is
• WHY the change was made
• HOW a consumer should update their code

5. Once you are happy with the changeset, commit the file to your branch.

Changesets are designed to stack, so there's no problem with adding multiple. You might want to add more than one changeset when:

• You want to release multiple packages with different changelog entries
• You have made multiple changes to a package that should each be called out separately