morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[GH-ISSUE #4881] [Bug] [macOS] Installation via Claude Desktop app requires deprecated Nodejs framework "prebuild-install@7.1.3" #3033

New issue

Closed

opened 2026-10-31 00:35:09 +00:00 by bsakaguchi · 5 comments

bsakaguchi commented

2026-10-31 00:35:09 +00:00

Owner

Originally created by @3pLe-A on GitHub (Oct 17, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/4881

Before submitting

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

Area

Setup, packaging, or upgrade

Observed behavior

During installation of REA, on th step of Choosing an Agent, when choosing Claude Desktop app and typing this in Terminal:

npx rea-agents@latest setup --client claude_desktop

I get this type of error:

Need to install the following packages:
rea-agents@6.5.0
Ok to proceed? (y) y
npm warn deprecated prebuild-install@7.1.3: No longer maintained. Please contact the author of the relevant native addon; alternatives are available.
│
◆  Ready to review
│
│  INSTALL  Hopper deep-analysis provider
│          /Users/<username>/Applications/Hopper Disassembler.app
│          network: https://www.hopperapp.com/include/files-api.php?request=releases&public=true
│          network: https://www.hopperapp.com:443/downloader/public/
│          command: hdiutil attach -readonly -nobrowse -mountpoint <private-mount> <verified-hopper.dmg>
│          command: codesign --verify --deep --strict <mounted-hopper.app>
│          command: codesign --verify --strict '-R= identifier "com.cryptic-apps.hopper-web-4" and anchor apple generic and certificate leaf[subject.OU] = "2AMA2753NF"' <mounted-hopper.app>
│          command: ditto <mounted-hopper.app> <user-Applications-stage>
│          command: open <installed-hopper.app>
│          Download the official Hopper package, verify it, and install it. Hopper may show its demo or license prompt when first opened.
│          external software
│
│  UPDATE  Claude Desktop
│          /Users//<username>/Library/Application Support/Claude/claude_desktop_config.json
│          backup: /Users/<username>/Library/Application Support/Claude/claude_desktop_config.json.rea.backup
│          Add the REA MCP registration for Claude Desktop; preserve unrelated configuration. The backup path reflects the configuration inspected for this plan; if that file changes before execution, setup will select a recovery path for its current contents. Command: "npx" "-y" "rea-agents@6.5.0" "mcp". No additional provider environment variables. Existing server environment overrides are retained. If this plan installs Hopper, REA will add HOPPER_LAUNCHER_PATH using the launcher path reported by that installation. Quit Claude Desktop fully before approving; closing its window is not enough. A running Claude Desktop can rewrite this file from memory and drop the registration. Start it again after setup.
│
│  INSTALL  REA reverse-engineering skill
│          /Users/<username>/.agents/skills/reverse-engineer-anything
│          Install or update the bundled REA reverse-engineering skill and on-demand references.
│
│  REA will preserve unrelated configuration and will not install or upgrade Node.js, npm, Homebrew, Java, or Ghidra.
│
◆  Apply these 3 changes?
│  ● Yes, apply / ○ No, cancel

I don't know whether installing prebuild-install@7.1.3 package can be considered part of the installation script, but it seems worthy of pointing it out.

Reproduction

I ran all the recommended steps according to the developer website:

1. Prepare your computer

1.1. Open Terminal
1.2. Downloaded official Node.js LTS version using this chain of commands (given by official website):

# Download and install nvm:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.8/install.sh | bash

# in lieu of restarting the shell
\. "$HOME/.nvm/nvm.sh"

# Download and install Node.js:
nvm install 24

# Verify the Node.js version:
node -v # Should print "v24.22.0".
v26.5.0
# Verify npm version:
npm -v # Should print "11.19.1".
11.17.0

1.3. Made a working dir:

mkdir rev_eng_any && cd rev_eng_any

2. Choose a coding agent

2.1. Used the codeline provided on the REA website:

npx rea-agents@latest setup --client claude_desktop

2.2. It asked whether I want to proceed with installation. Answer was yes:

Need to install the following packages:
rea-agents@6.5.0
Ok to proceed? (y) y

2.3. After that I got the warn message about deprecated package and asked whether I want to apply the changes given in "Observed behavior"

Expected behavior

Actually do not know whether this package provided by Nodejs is necessary or not if it's deprecated by the developers themselves.

Impact and scope

Unknown.

REA version

REA is still not installed

Runtime and platform

Node.js version 26.5.0; macOS Sonoma 14.7.4; arm64 (M1)

Target and artifact context

No response

Interface

CLI

Earliest failure stage

Unknown

Relevant output or evidence

Typed outcome or recovery expected

No response

Analysis or suspected cause

No response

Additional context

No response

Originally created by @3pLe-A on GitHub (Oct 17, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/4881 ### 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. ### Area Setup, packaging, or upgrade ### Observed behavior During installation of REA, on th step of Choosing an Agent, when choosing Claude Desktop app and typing this in Terminal: ``` npx rea-agents@latest setup --client claude_desktop ``` I get this type of error: ``` Need to install the following packages: rea-agents@6.5.0 Ok to proceed? (y) y npm warn deprecated prebuild-install@7.1.3: No longer maintained. Please contact the author of the relevant native addon; alternatives are available. │ ◆ Ready to review │ │ INSTALL Hopper deep-analysis provider │ /Users/<username>/Applications/Hopper Disassembler.app │ network: https://www.hopperapp.com/include/files-api.php?request=releases&public=true │ network: https://www.hopperapp.com:443/downloader/public/ │ command: hdiutil attach -readonly -nobrowse -mountpoint <private-mount> <verified-hopper.dmg> │ command: codesign --verify --deep --strict <mounted-hopper.app> │ command: codesign --verify --strict '-R= identifier "com.cryptic-apps.hopper-web-4" and anchor apple generic and certificate leaf[subject.OU] = "2AMA2753NF"' <mounted-hopper.app> │ command: ditto <mounted-hopper.app> <user-Applications-stage> │ command: open <installed-hopper.app> │ Download the official Hopper package, verify it, and install it. Hopper may show its demo or license prompt when first opened. │ external software │ │ UPDATE Claude Desktop │ /Users//<username>/Library/Application Support/Claude/claude_desktop_config.json │ backup: /Users/<username>/Library/Application Support/Claude/claude_desktop_config.json.rea.backup │ Add the REA MCP registration for Claude Desktop; preserve unrelated configuration. The backup path reflects the configuration inspected for this plan; if that file changes before execution, setup will select a recovery path for its current contents. Command: "npx" "-y" "rea-agents@6.5.0" "mcp". No additional provider environment variables. Existing server environment overrides are retained. If this plan installs Hopper, REA will add HOPPER_LAUNCHER_PATH using the launcher path reported by that installation. Quit Claude Desktop fully before approving; closing its window is not enough. A running Claude Desktop can rewrite this file from memory and drop the registration. Start it again after setup. │ │ INSTALL REA reverse-engineering skill │ /Users/<username>/.agents/skills/reverse-engineer-anything │ Install or update the bundled REA reverse-engineering skill and on-demand references. │ │ REA will preserve unrelated configuration and will not install or upgrade Node.js, npm, Homebrew, Java, or Ghidra. │ ◆ Apply these 3 changes? │ ● Yes, apply / ○ No, cancel ``` I don't know whether installing `prebuild-install@7.1.3` package can be considered part of the installation script, but it seems worthy of pointing it out. ### Reproduction I ran all the recommended steps according to the developer website: ### 1. Prepare your computer 1.1. Open Terminal 1.2. Downloaded official Node.js LTS version using this chain of commands (given by official [website](https://nodejs.org/en/download)): ``` # Download and install nvm: curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.8/install.sh | bash # in lieu of restarting the shell \. "$HOME/.nvm/nvm.sh" # Download and install Node.js: nvm install 24 # Verify the Node.js version: node -v # Should print "v24.22.0". v26.5.0 # Verify npm version: npm -v # Should print "11.19.1". 11.17.0 ``` 1.3. Made a working dir: ``` mkdir rev_eng_any && cd rev_eng_any ``` ### 2. Choose a coding agent 2.1. Used the codeline provided on the REA website: ``` npx rea-agents@latest setup --client claude_desktop ``` 2.2. It asked whether I want to proceed with installation. Answer was yes: ``` Need to install the following packages: rea-agents@6.5.0 Ok to proceed? (y) y ``` 2.3. After that I got the warn message about deprecated package and asked whether I want to apply the changes given in "Observed behavior" ### Expected behavior Actually do not know whether this package provided by Nodejs is necessary or not if it's deprecated by the developers themselves. ### Impact and scope Unknown. ### REA version REA is still not installed ### Runtime and platform Node.js version 26.5.0; macOS Sonoma 14.7.4; arm64 (M1) ### Target and artifact context _No response_ ### Interface CLI ### Earliest failure stage Unknown ### Relevant output or evidence <img width="2560" height="1532" alt="Image" src="https://github.com/user-attachments/assets/93a3f56f-d4fc-4640-b143-be9493d03a64" /> ### Typed outcome or recovery expected _No response_ ### Analysis or suspected cause _No response_ ### Additional context _No response_

bsakaguchi

2026-10-31 00:35:09 +00:00

closed this issue
added the
triage

bug
labels

bsakaguchi commented

2026-10-31 00:35:10 +00:00

Author

Owner

@morluto commented on GitHub (Oct 17, 2026):

I traced this warning against the current lockfile and the npm registry metadata for the published packages:

rea-agents@6.5.0 → optional frida@17.23.2 → prebuild-install@^7.1.3.

The registry marks prebuild-install@7.1.3 deprecated. It is Frida's native-addon installation helper; it is not Node.js itself or an extra framework selected by Claude Desktop setup. The warning is emitted while npm resolves/installs REA's dependency tree, before REA shows its setup plan.

The output here reaches Apply these 3 changes?, so this evidence does not establish that setup failed. The upstream dependency maintenance concern is still valid; leaving this report open. Removing or replacing this helper requires a compatible Frida packaging change, rather than suppressing the warning or making an unrelated Node/npm upgrade.

Evidence: published REA metadata, published Frida metadata, deprecated helper metadata. This was a metadata/source investigation; no fresh installation or Hopper installation was run.

@morluto commented on GitHub (Oct 17, 2026): I traced this warning against the current lockfile and the npm registry metadata for the published packages: `rea-agents@6.5.0` → optional `frida@17.23.2` → `prebuild-install@^7.1.3`. The registry marks `prebuild-install@7.1.3` deprecated. It is Frida's native-addon installation helper; it is not Node.js itself or an extra framework selected by Claude Desktop setup. The warning is emitted while npm resolves/installs REA's dependency tree, before REA shows its setup plan. The output here reaches **Apply these 3 changes?**, so this evidence does not establish that setup failed. The upstream dependency maintenance concern is still valid; leaving this report open. Removing or replacing this helper requires a compatible Frida packaging change, rather than suppressing the warning or making an unrelated Node/npm upgrade. Evidence: [published REA metadata](https://registry.npmjs.org/rea-agents/6.5.0), [published Frida metadata](https://registry.npmjs.org/frida/17.23.2), [deprecated helper metadata](https://registry.npmjs.org/prebuild-install/7.1.3). This was a metadata/source investigation; no fresh installation or Hopper installation was run.

bsakaguchi commented

2026-10-31 00:35:11 +00:00

Author

Owner

@3pLe-A commented on GitHub (Oct 17, 2026):

Ok.

@3pLe-A commented on GitHub (Oct 17, 2026): Ok.

bsakaguchi commented

2026-10-31 00:35:11 +00:00

Author

Owner

@3pLe-A commented on GitHub (Oct 17, 2026):

Addiitonal context:
After agreeing with changes I get this output:

│  Yes, apply
◇  Hopper deep-analysis provider
◆  Hopper deep-analysis provider · /Users/<username>/Applications/Hopper Disassembler.app/Contents/MacOS/hopper
◇  Claude Desktop
◆  Claude Desktop
◇  REA reverse-engineering skill
◆  REA reverse-engineering skill
!  Open Hopper, choose its demo mode or activate a license, then rerun rea doctor --json.
│
└  Run `npx rea-agents doctor` for the remaining checks.

I ran rea doctor --json and it gave an error:

~ rea doctor --json
-bash: rea: command not found

I ran npx rea-agents doctor, and it gave the output (see output_npx.log file)

output_npx.log

@3pLe-A commented on GitHub (Oct 17, 2026): Addiitonal context: After agreeing with changes I get this output: ``` │ Yes, apply ◇ Hopper deep-analysis provider ◆ Hopper deep-analysis provider · /Users/<username>/Applications/Hopper Disassembler.app/Contents/MacOS/hopper ◇ Claude Desktop ◆ Claude Desktop ◇ REA reverse-engineering skill ◆ REA reverse-engineering skill ! Open Hopper, choose its demo mode or activate a license, then rerun rea doctor --json. │ └ Run `npx rea-agents doctor` for the remaining checks. ``` I ran `rea doctor --json` and it gave an error: ``` ~ rea doctor --json -bash: rea: command not found ``` I ran `npx rea-agents doctor`, and it gave the output (see `output_npx.log` file) [output_npx.log](https://github.com/user-attachments/files/33610653/output_npx.log)

bsakaguchi commented

2026-10-31 00:35:11 +00:00

Author

Owner

@XinwangTao commented on GitHub (Oct 18, 2026):

Worth noting the warning comes from a transitive native-addon dependency (prebuild-install is used by packages like @napi-rs or similar binary packages at install time), not from REA itself — so it's cosmetic for users as long as the binary downloads succeed. Tracking the deprecated helper metadata updates is the right way to resolve it upstream; until then a one-line note in setup docs (that the warning is expected and harmless if install completes) would prevent users from treating it as a failure.

@XinwangTao commented on GitHub (Oct 18, 2026): Worth noting the warning comes from a transitive native-addon dependency (prebuild-install is used by packages like @napi-rs or similar binary packages at install time), not from REA itself — so it's cosmetic for users as long as the binary downloads succeed. Tracking the deprecated helper metadata updates is the right way to resolve it upstream; until then a one-line note in setup docs (that the warning is expected and harmless if install completes) would prevent users from treating it as a failure.

bsakaguchi commented

2026-10-31 00:35:11 +00:00

Author

Owner

@3pLe-A commented on GitHub (Oct 19, 2026):

Thanks for giving attention to this minor issue and fixing it. I will close this issue.

@3pLe-A commented on GitHub (Oct 19, 2026): Thanks for giving attention to this minor issue and fixing it. I will close this issue.

bsakaguchi referenced this issue

2026-10-31 01:07:39 +00:00

[PR #3033] [CLOSED] fix(browser): keep metadata-budget fixture scripts alive across captures #5570

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#3033

No description provided.

Rows
Columns