[PR #5012] [MERGED] docs(setup): clarify prebuild-install warning from optional dependencies (#4881) #6730

Closed
opened 2026-11-01 21:42:38 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5012
Author: @prasad2512
Created: 10/18/2026
Status: ✅ Merged
Merged: 10/21/2026
Merged by: @morluto

Base: main ← Head: docs/issue-4881-prebuild-install-note


📝 Commits (1)

  • e5be6e5 docs(setup): clarify prebuild-install warning from optional dependencies (#4881)

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 docs/installation.md (+4 -0)

📄 Description

Summary

During npx rea-agents@latest setup, npm may print npm warn deprecated prebuild-install@7.1.3: No longer maintained. Please contact the author of the relevant native addon; alternatives are available.. This warning originates from the upstream dependency tree of optional native dependencies (specifically Frida) and is cosmetic: it does not indicate a setup failure or prevent REA from installing.

This PR adds a concise note in docs/installation.md under ## Start setup clarifying that the deprecation warning is expected and harmless, preventing users from mistaking it for an installation failure.

Fixes #4881

Problem and expected behavior

Users running npx rea-agents@latest setup --client claude_desktop encounter the deprecation warning for prebuild-install@7.1.3 emitted by npm during dependency resolution, leading them to suspect setup failure or unsupported environment requirements. The setup guide should clarify that this message is an expected upstream transitive warning from optional Frida dependencies and does not block setup.

Change and scope

Adds a 3-line note in docs/installation.md directly under the ## Start setup snippet. No runtime or configuration code changes.

Contract and boundary impact

  • Semantic owner and earliest changed stage: documentation

  • Contribution scope fit and linked maintainer decision: not applicable

  • CLI and MCP/tool-catalog contract: none

  • Provider, bridge, target-format, or platform compatibility: all platforms

  • Evidence, artifact, provenance, or reconstruction contract: none

  • Target selection, authority, upstream behavior, and cleanup details: not applicable

  • Generated metadata: none

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests added or updated: none (documentation only)
  • Base reproduction or other evidence: reported in #4881

Validation performed

  • npx oxfmt docs/installation.md — passed (clean formatting)
  • npm run check:fast — passed (0 errors)

Compatibility, safety, and release

  • Breaking changes or migration steps: none
  • Real Hopper/Ghidra, browser, or OS coverage: documentation only
  • Package or release metadata impact: none
  • Security, privacy, process, or containment review: safe

Author readiness

Human owner: @prasad2512

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/5012 **Author:** [@prasad2512](https://github.com/prasad2512) **Created:** 10/18/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `docs/issue-4881-prebuild-install-note` --- ### 📝 Commits (1) - [`e5be6e5`](https://github.com/morluto/rea/commit/e5be6e5af45601275346fb4d6b6981a443f76b73) docs(setup): clarify prebuild-install warning from optional dependencies (#4881) ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+4 -0) </details> ### 📄 Description ## Summary During `npx rea-agents@latest setup`, npm may print `npm warn deprecated prebuild-install@7.1.3: No longer maintained. Please contact the author of the relevant native addon; alternatives are available.`. This warning originates from the upstream dependency tree of optional native dependencies (specifically Frida) and is cosmetic: it does not indicate a setup failure or prevent REA from installing. This PR adds a concise note in `docs/installation.md` under `## Start setup` clarifying that the deprecation warning is expected and harmless, preventing users from mistaking it for an installation failure. Fixes #4881 ## Problem and expected behavior Users running `npx rea-agents@latest setup --client claude_desktop` encounter the deprecation warning for `prebuild-install@7.1.3` emitted by npm during dependency resolution, leading them to suspect setup failure or unsupported environment requirements. The setup guide should clarify that this message is an expected upstream transitive warning from optional Frida dependencies and does not block setup. ## Change and scope Adds a 3-line note in `docs/installation.md` directly under the `## Start setup` snippet. No runtime or configuration code changes. ## Contract and boundary impact - Semantic owner and earliest changed stage: documentation - Contribution scope fit and linked maintainer decision: not applicable - CLI and MCP/tool-catalog contract: none - Provider, bridge, target-format, or platform compatibility: all platforms - Evidence, artifact, provenance, or reconstruction contract: none - Target selection, authority, upstream behavior, and cleanup details: not applicable - Generated metadata: none - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: none (documentation only) - Base reproduction or other evidence: reported in #4881 ## Validation performed - `npx oxfmt docs/installation.md` — passed (clean formatting) - `npm run check:fast` — passed (0 errors) ## Compatibility, safety, and release - Breaking changes or migration steps: none - Real Hopper/Ghidra, browser, or OS coverage: documentation only - Package or release metadata impact: none - Security, privacy, process, or containment review: safe ## Author readiness Human owner: @prasad2512 - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:42:38 +00:00
Sign in to join this conversation.
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#6730
No description provided.