Commit 0c111f8
fix: remove Buffer dependency, accept Uint8Array keys
- Replace all Node.js Buffer usage in base64.ts with browser-compatible
btoa/atob + Uint8Array (fixes "Buffer is not defined" in Chrome
service workers, breaking NIP-04 encrypt/decrypt)
- Make signEvent, getPublicKeySync, and finalizeEvent in crypto.ts
accept both hex string and Uint8Array for private key parameter
(fixes "hex string expected, got object" when callers pass bytes)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>1 parent 1f6eaba commit 0c111f8
18 files changed
Lines changed: 180 additions & 82 deletions
File tree
- dist
- browser
- cjs
- encoding
- esm
- encoding
- types
- encoding
- src
- encoding
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments