chore(deps): bump nostr-tools from 1.17.0 to 2.3.2

[dependabot[bot]]

Bumps nostr-tools from 1.17.0 to 2.3.2.

Release notes

Sourced from nostr-tools's releases.

v2.0.0

The "core" API has been modified to be simpler, but it didn't really change much since there wasn't much to change. Most names were changed though. Deprecated methods were removed. The <number> type parameter on Event was removed (sorry @​alexgleason) and kinds are not enums anymore, they are just constants in the nostr-tools/kinds module.

Ability to import individual modules has been introduced (thanks to @​fr4nzap) (technically I think it was already released but doesn't matter), which will lead to much less bloated bundles when you just want a small piece of functionality.

The relay.ts and pool.ts modules were rewritten from scratch with no regards for backwards compatibility, but most of the actual functionality was kept (a notable exception were the batched requests from @​sepehr-safari). Their code is more solid and simpler to read and understand now now and makes less compromises.

Ability to use this module optionally with nostr-wasm was introduced.

Some other NIP helpers were introduced, like NIP-11 and some other I forgot. But more will come soon now.

Upgrade guide

• keys.ts and event.ts files were merged into a single pure.ts module -- which is equivalent to wasm.ts
• generatePrivateKey() was renamed to generateSecretKey() and now returns a Uint8Array instead of a hex string;
• getPublicKey() now takes a Uint8Array instead of a hex string, it still returns a public as a hex string though;
• finishEvent() was renamed to finalizeEvent() and now takes a Uint8Array secret key instead of a hex string;
• nip19.nsecEncode() also expects a Uint8Array now and nip19.decode() returns a Uint8Array when it finds an nsec;
• There are too many changes in nostr-tools/relay and nostr-tools/pool, so I won't write them here.

Thank you for your patience.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.