Use node:crypto chacha20-poly1305 on deno

Author: kigawas

.github/workflows/ci.yml

@@ -72,6 +72,8 @@ jobs:
 
       - run: pnpm install && pnpm build && cd example && pnpm install
 
+      - run: deno task test
+
       - name: check main.js
         run: |
           ./scripts/check-runtime.sh example/main.js

CHANGELOG.md

@@ -4,6 +4,7 @@
 
 - Bump dependencies
 - Bump emitted JavaScript target to es2021
+- Use `node:crypto`'s chacha20-poly1305 implementation on deno (>=2.7.10)
 
 ## 0.2.5
 

README.md

@@ -17,7 +17,7 @@ Otherwise (e.g. browser, react native), it'll use [`@noble/ciphers`](https://git
 | ------------ | ---------------- | ---------------- |
 | Node         | `node:crypto` ⚡  | `node:crypto` ⚡  |
 | Bun          | `node:crypto` ⚡  | `@noble/ciphers` |
-| Deno         | `node:crypto` ⚡  | `@noble/ciphers` |
+| Deno         | `node:crypto` ⚡  | `node:crypto` ⚡  |
 | Browser      | `@noble/ciphers` | `@noble/ciphers` |
 | React Native | `@noble/ciphers` | `@noble/ciphers` |
 
@@ -66,6 +66,6 @@ If key is fixed and nonce is less than 16 bytes, **avoid randomly generated nonc
 
 ## Known limitations
 
-- `xchacha20-poly1305` is implemented with pure JS [`hchacha20`](https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-xchacha#section-2.2) function and `node:crypto`'s `chacha20-poly1305` on node.
-- Currently (Apr 2026), `node:crypto`'s `chacha20-poly1305` is neither supported on [deno](https://github.com/denoland/deno/issues/28411) nor [bun](https://github.com/oven-sh/bun/issues/8072), `@noble/ciphers`'s implementation is used on both platforms instead.
+- `xchacha20-poly1305` is implemented with pure JS [`hchacha20`](https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-xchacha#section-2.2) function and `node:crypto`'s `chacha20-poly1305` on node/deno.
+- Currently (Apr 2026), `node:crypto`'s `chacha20-poly1305` is not supported on [bun](https://github.com/oven-sh/bun/issues/8072), `@noble/ciphers`'s implementation is used instead. From deno 2.7.10, `node:crypto`'s `chacha20-poly1305` is [supported](https://github.com/denoland/deno/issues/28411). Please upgrade deno to use native implementation for better performance.
 - Some old versions of `deno` [did not support](https://github.com/denoland/deno/discussions/17964#discussioncomment-10917259) **indirect** conditional exports. For example, if a library uses `@ecies/ciphers`, client code of that library might fall back to the `node:crypto` implementation and would not work properly, specifically `aes-256-gcm` and `chacha20-poly1305`. If you found such a problem, upgrade deno and run with `--conditions deno` (>=2.4.0) or `--unstable-node-conditions deno`(>=2.3.6,<2.4.0).

example/main.js

@@ -1,5 +1,5 @@
 import { aes256cbc, aes256gcm } from "@ecies/ciphers/aes";
-import { xchacha20 } from "@ecies/ciphers/chacha";
+import { chacha20, xchacha20 } from "@ecies/ciphers/chacha";
 
 import { randomBytes } from "@noble/ciphers/webcrypto";
 
@@ -27,6 +27,12 @@ const ciphers = [
     callback: aes256cbc,
     aad: undefined,
   },
+  {
+    keyLength: 32,
+    nonceLength: 12,
+    callback: chacha20,
+    aad: randomBytes(16),
+  },
   {
     keyLength: 32,
     nonceLength: 24,

package.json

@@ -15,7 +15,7 @@
   "engines": {
     "node": ">=16",
     "bun": ">=1",
-    "deno": ">=2"
+    "deno": ">=2.7.10"
   },
   "keywords": [
     "cryptography",
@@ -45,7 +45,7 @@
       "types": "./dist/chacha/node.d.ts",
       "browser": "./dist/chacha/noble.js",
       "react-native": "./dist/chacha/noble.js",
-      "deno": "./dist/chacha/noble.js",
+      "deno": "./dist/chacha/node.js",
       "bun": "./dist/chacha/noble.js",
       "default": "./dist/chacha/node.js"
     }