From a24a0ec9139b36a9c2e20699cdfc8e43347bef4f Mon Sep 17 00:00:00 2001
From: Tam Nguyen Duc <1218621+tamnd@users.noreply.github.com>
Date: Fri, 21 Aug 2026 19:01:38 +0700
Subject: [PATCH] Let the Deno run spawn a child, so the watch test runs (#27)

The progress test spawns a node process and watches the file it
writes, which under Deno is run access and the command did not ask
for it. So the test threw NotCapable rather than failing on an
assertion, and it had never run under Deno at all: the one job that
covers the watch path on that runtime was covering nothing.

With --allow-run the suite is 355 passed, 0 failed, 8 ignored on
deno 2.9.5, the same version CI installs, and the watch test takes
123 ms, so the child really did spawn and really did exit. Nothing
else in the suite needs it, and node keeps running the same test the
same way.
---
 package.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/package.json b/package.json
index 057af1e..2763ab1 100644
--- a/package.json
+++ b/package.json
@@ -64,7 +64,7 @@
     "test": "node --test \"test/*.test.mjs\"",
     "test:temporal": "node --harmony-temporal --test \"test/*.test.mjs\"",
     "test:bun": "bun test --timeout 60000 test/",
-    "test:deno": "deno test --no-check --allow-read --allow-write --allow-env --allow-ffi \"test/*.test.mjs\"",
+    "test:deno": "deno test --no-check --allow-read --allow-write --allow-env --allow-ffi --allow-run \"test/*.test.mjs\"",
     "check:types": "tsc --noEmit --project test/types/tsconfig.json",
     "check:package": "attw --pack .",
     "check:api": "api-extractor run --verbose",