[GH-ISSUE #7742] [Feature] recover_javascript_sources on Windows x64 #4635

New issue

Open

opened 2026-10-31 00:51:38 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:51:38 +00:00

Owner

Originally created by @jgt87 on GitHub (Oct 28, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/7742

Before submitting

I searched the open and closed issues for a related report.
I removed credentials, tokens, private paths, and sensitive target data.

Reproduced on rea-agents 6.8.0 (released) and on main 6a226bd09: both return the
same capability_unavailable message (shown below) on Windows 11.

Area

JavaScript source recovery (recover_javascript_sources, Wakaru engine).

Current limitation

docs/javascript-recovery.md states: "REA accepts Wakaru ^1.13.0 on Linux
x64", and the adapter bounds the Wakaru process with util-linux prlimit. On
Windows the tool is unavailable, so a Windows user cannot recover readable
sources from a bundle without a Linux machine or WSL.

Use cases

Recover module boundaries and readable sources from a production bundle on a
Windows workstation, next to analyze_javascript_application, which already
runs on Windows.

Desired outcome and success criteria

Either:

Support a Windows x64 Wakaru build (if one is published), with the process
bounded by the Windows native controls REA already ships for other workers
(for example a job object with a memory limit) instead of prlimit; or
Document a supported path for Windows users (WSL, with the exact command),
and say so in the tool's unavailable-capability message.

Success: recover_javascript_sources runs on Windows x64, or the refusal names
the supported alternative.

Expected interaction with targets

Reads existing files and launches the Wakaru process (as on Linux).

#4948 (recover_javascript_sources is Linux-x64-gated even though Wakaru ships a native darwin-arm64 build)
PR #5324 (run Wakaru on macOS arm64 with shell resource limits)

Verification available so far

rea-agents 6.8.0 (npm, Node 26.12.1) and upstream main at 6a226bd09 (source, Node 24.22.1), Windows 11 Pro
(10.0.26300), without
REA_WAKARU_COMMAND set:

$ rea recover-javascript-sources C:\...\index.js C:\...\out --format json
{"code":"capability_unavailable","category":"unsupported_provider","message":"Provide an absolute REA_WAKARU_COMMAND pointing to a Wakaru ^1.13.0 Linux x64 binary (verified with 1.14.0); no tool is installed by REA. See docs/javascript-recovery.md#install-wakaru."}

The message asks for a Linux x64 binary on a Windows host. I did not check
whether Wakaru publishes a Windows x64 binary.

Originally created by @jgt87 on GitHub (Oct 28, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7742 ## Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. Reproduced on rea-agents 6.8.0 (released) and on main 6a226bd09: both return the same `capability_unavailable` message (shown below) on Windows 11. ## Area JavaScript source recovery (`recover_javascript_sources`, Wakaru engine). ## Current limitation `docs/javascript-recovery.md` states: "REA accepts Wakaru ^1.13.0 on Linux x64", and the adapter bounds the Wakaru process with util-linux `prlimit`. On Windows the tool is unavailable, so a Windows user cannot recover readable sources from a bundle without a Linux machine or WSL. ## Use cases - Recover module boundaries and readable sources from a production bundle on a Windows workstation, next to `analyze_javascript_application`, which already runs on Windows. ## Desired outcome and success criteria Either: 1. Support a Windows x64 Wakaru build (if one is published), with the process bounded by the Windows native controls REA already ships for other workers (for example a job object with a memory limit) instead of `prlimit`; or 2. Document a supported path for Windows users (WSL, with the exact command), and say so in the tool's unavailable-capability message. Success: `recover_javascript_sources` runs on Windows x64, or the refusal names the supported alternative. ## Expected interaction with targets Reads existing files and launches the Wakaru process (as on Linux). ## Related - #4948 (`recover_javascript_sources` is Linux-x64-gated even though Wakaru ships a native darwin-arm64 build) - PR #5324 (run Wakaru on macOS arm64 with shell resource limits) ## Verification available so far rea-agents 6.8.0 (npm, Node 26.12.1) and upstream `main` at 6a226bd09 (source, Node 24.22.1), Windows 11 Pro (10.0.26300), without `REA_WAKARU_COMMAND` set: ```text $ rea recover-javascript-sources C:\...\index.js C:\...\out --format json {"code":"capability_unavailable","category":"unsupported_provider","message":"Provide an absolute REA_WAKARU_COMMAND pointing to a Wakaru ^1.13.0 Linux x64 binary (verified with 1.14.0); no tool is installed by REA. See docs/javascript-recovery.md#install-wakaru."} ``` The message asks for a Linux x64 binary on a Windows host. I did not check whether Wakaru publishes a Windows x64 binary.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#4635

No description provided.

Rows
Columns