The analysis counted zero bridges. The app exposes 51 methods.

Description and use

REA identified 51 methods in the ElectronFiddle bridge after isolating and correcting the minified code, confirming that static analysis can be accurate with proper configuration.

Problem

Determine how a desktop app’s window communicates with its main process and identify exposed bridges and IPC operations.

Outcome

REA initially missed the app’s own bridge due to heap budget and unknown node handling. By isolating the preload file and correcting the webpack alias, REA accurately reported 1 bridge with 51 members and 48 dynamic IPC operations, confirming the static analysis matches the source.

Workflow

• 1. Download Electron Fiddle macOS arm64 zip and extract app.asar.
• 2. Run npx -y rea-agents@latest analyze-javascript-application /abs/path/app.asar --json > fiddle.json to analyze the bundle.
• 3. Review REA JSON summary for context bridges and IPC counts.
• 4. Identify missing bridge due to unknown nodes and heap budget limits.
• 5. Copy the preload file to a separate folder and re‑run REA on it alone.
• 6. Modify the minified require alias to require("electron") and re‑run REA.
• 7. Verify the bridge and IPC counts match the source code.
• 8. Compare results with unbundled source for validation.

Evidence

REA inventoried 89 files, parsed 71 JavaScript files and visited 2,386,900 syntax nodes without executing a line of the app.

Source

The preload that defines the bridge is a 9,768-byte file. REA parsed it completely, then attached two unknown nodes to it.

Source

I changed one expression in my copy, _(288) to require("electron")... context_bridge_apis: 1 (ElectronFiddle, 51 members, 0 unknown) ipc.operations: 48 ipc.dynamic_channel_operations: 48

Source