From 14deaaa5b6675d6fa4ca2f1edfb67c0a41e922ed Mon Sep 17 00:00:00 2001
From: Copilot <198982749+Copilot@users.noreply.github.com>
Date: Tue, 25 Nov 2025 12:03:16 -0600
Subject: [PATCH] Re-enable wasm-pack test after upstream issue fix (#508)

* Initial plan

* Re-enable wasm-pack test and update Node.js to v22

Co-authored-by: anakrish <35780660+anakrish@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: anakrish <35780660+anakrish@users.noreply.github.com>
---
 .github/workflows/test-wasm.yml | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/test-wasm.yml b/.github/workflows/test-wasm.yml
index f26a684..3a27b0b 100644
--- a/.github/workflows/test-wasm.yml
+++ b/.github/workflows/test-wasm.yml
@@ -24,7 +24,7 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
-          node-version: 18
+          node-version: 22
 
       - name: Install wasmlpack
         run: cargo install wasm-pack
@@ -35,7 +35,5 @@ jobs:
           cargo fetch
           cargo clippy --all-targets --no-deps -- -Dwarnings
           wasm-pack build --target nodejs --release
-          # Enable when upstream issue is fixed.
-          # https://github.com/microsoft/regorus/issues/371
-          # wasm-pack test --release --node
+          wasm-pack test --release --node
           node test.js