From source
Only needed to change Wasit itself, or to run the bundled fixture servers that let you try a full settlement run against something you control.
git clone https://github.com/wasit-dev/wasit.git
cd wasit
npm install
npm run build
cp .env.example .envOn Windows PowerShell the last line is:
Copy-Item .env.example .envNote — build order matters.
npm run buildbuilds core first, then the CLI and the server, because both compile against core's emitted type declarations rather than its source. Building a package on its own after changing core will typecheck against the previous build.
Run the checks against your own fixtures
Three fixture servers ship with the repo — real servers built on the official SDKs, not mocks. Each runs in its own terminal:
npx tsx packages/core/test/fixtures/x402-real-server.ts
npx tsx packages/core/test/fixtures/mpp-charge-server.ts
npx tsx packages/core/test/fixtures/mpp-channel-server.tsThen point the CLI at them:
node packages/cli/dist/index.js test --target http://localhost:3001/protectedTests
The whole suite is offline: no keys, no target, no network. Run
npm run build before npm run typecheck -w packages/cli, since the CLI
typechecks against core's compiled declarations.