feat(sdk): support signing on edge and browser runtimes - #1
Open
timo126 wants to merge 1 commit into
Open
Conversation
Enable settlement signing in edge and browser runtimes while retaining the Node.js fallback, and document supported runtimes. Closes accensa#101 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds portable Ed25519 settlement signing for
@accensa/sdk, enabling route-attribution reports from edge and browser-compatible runtimes while preserving Node.js support.Changes
globalThis.crypto?.subtleand attempts WebCrypto Ed25519 first.node:cryptoonly when WebCrypto is unavailable or does not support Ed25519.Verification
pnpm --filter @accensa/sdk test— 117 tests passed.pnpm --filter @accensa/sdk typecheck— passed.git diff --check— passed.Compatibility
Signatures remain Ed25519 signatures over the exact UTF-8 request body and continue to use the existing
X-Signatureheader, so the/api/hook/settleverification contract is unchanged.Closes accensa#101