This repo contains 3 npm packages:

• @tbdex/protocol - create, parse, verify, and validate the tbdex messages and resources defined in the protocol draft specification
• @tbdex/http-client - An HTTP client that can be used to send tbdex messages to PFIs
• @tbdex/http-server - A configurable implementation of the tbdex http api draft specification

This multi-package repository uses pnpm workspaces.

This repository uses git submodules. To clone this repo with submodules

git clone --recurse-submodules [email protected]:TBD54566975/tbdex-js.git

Or to add submodules after cloning

git submodule update --init

We recommend running the command below once which will configure your environment to only checkout the hosted directory under the tbdex git submodule directory, which contains files relevant to this repo, such as tbDEX spec test vectors and schemas.

git -C tbdex sparse-checkout set hosted

This project uses hermit to manage tooling like node. See this page to set up Hermit on your machine - make sure to download the open source build and activate it for the project

Currently, we have these packages installed via Hermit (can also view by checking out hermit status):

• node
• pnpm

You can run hermit upgrade {package} to upgrade an existing package, or hermit install {package} to install a new package. Please see Hermit package management page for more details.

0. clone the repo and cd into the project directory
1. Install all project dependencies by pnpm install
2. Build all workspace projects in this repo by running npm run build
3. run tests using pnpm test:node to run tests within a nodejs runtime
4. run tests using pnpm test:browser to run tests within a browser runtime. Before doing so, run npx playwright install --with-deps, only required once.

This project uses Changesets for semver management and releases. For motivations, see PR description here.

Release workflow:

1. Open a PR
2. changeset-bot will automatically comment on the PR with a reminder & recommendations for semver
3. Run pnpm changeset locally and push changes (.changeset/*.md). The CLI tool will walk you through a set of steps for you to define the semantic changes and create a randomly-named markdown file within .changeset/.
4. Merge PR into main.
5. Profit from the automated release pipeline:
   • Release Workflow will create a new Version Package PR, or update the existing one. For example, see this PR. This PR updates the version numbers in the relevant package.json files & also aggregates the Summary notes into the relevant CHANGELOG.md files.
   • When maintainers are ready to publish the new changes, they will merge that PR and the very same Release Workflow will automatically publish a new version to NPM, and publish the docs to https://tbd54566975.github.io/tbdex-js/

You will need to update the tbdex submodule to the latest from time to time:

git submodule update --remote

If you have made changes to the tbdex submodule, you should push your changes to the tbdex remote as well as pushing changes to tbdex-js.

cd tbdex
git push
cd ..
git push