Summary

Add | NodeJS.ArrayBufferView to data parameters in webcrypto.SubtleCrypto methods (importKey, encrypt, decrypt, sign, verify, digest, unwrapKey).

Problem

TypeScript 5.7+ infers Uint8Array<ArrayBufferLike> for new Uint8Array(n), which is not assignable to NodeJS.BufferSource (= NonSharedArrayBufferView | ArrayBuffer).

This causes type errors on all SubtleCrypto methods when passing a Uint8Array created via new Uint8Array(n) — a very common pattern:

```typescript
const key = new Uint8Array(32);
// ERROR: Argument of type 'Uint8Array' is not assignable to parameter of type 'BufferSource'
await webcrypto.subtle.importKey("raw", key, "AES-GCM", false, ["encrypt"]);
```

Root Cause

1. TS 5.7 made `Uint8Array` generic: `Uint8Array`
2. `new Uint8Array(32)` produces `Uint8Array` (default generic)
3. `NodeJS.BufferSource` requires `NonSharedArrayBufferView` = `ArrayBufferView`
4. `Uint8Array` is NOT assignable to `Uint8Array`

At runtime, `new Uint8Array(32)` always creates a view over a regular `ArrayBuffer`, and Node.js's `SubtleCrypto` accepts it without issue.

Solution

Add `NodeJS.ArrayBufferView` as an accepted type alongside `NodeJS.BufferSource` for data parameters. This matches Node.js's runtime behavior without modifying the `BufferSource` type itself (which follows the WebIDL spec).

Additive change — no existing signatures modified. All previously-compiling code continues to compile.

Methods Updated

• `importKey` (raw format overload) — `keyData`
• `encrypt` — `data`
• `decrypt` — `data`
• `sign` — `data`
• `verify` — `signature` + `data`
• `digest` — `data`
• `unwrapKey` — `wrappedKey`

Impact

Every Node.js + TypeScript developer using `webcrypto` in strict mode. Eliminates the need for `as any` or `as unknown as BufferSource` workarounds.

Contributed by Continuum Identity — maintainers of 2FApi, a zero-knowledge proof authentication protocol for APIs.