fix: only detect real .app bundle paths in pathToFuseFile

[claude]

Requested by Samuel Attard · Slack thread

Before

pathToFuseFile() (and the ad-hoc codesign reset in flipFuses()) decided whether the Electron binary lives inside a macOS .app bundle using pathToElectron.includes('.app'). That bare substring check false-positives whenever any ancestor directory merely contains .app in its name. For example, building from a project under /home/user/.app/electron-app/ (or a Windows folder like my.app.win) made the resolver believe it was on macOS and route into the bundle path, producing errors such as:

Error: ENOENT: no such file or directory, open '/home/user/.app/electron-app/dist/Frameworks/Electron Framework.framework/Electron Framework'

After

Only genuine macOS .app bundle paths are treated as bundles. Building from a directory whose name happens to contain .app on Linux/Windows resolves the Electron binary path unchanged, as expected.

How

Both .includes('.app') call sites are replaced with regexes that match the real bundle layout instead of an arbitrary substring:

• In pathToFuseFile(), the inner-binary branch now matches \.app[\\/]Contents[\\/]MacOS[\\/] — i.e. the actual Something.app/Contents/MacOS/… structure that precedes the ../../Frameworks/… resolution.
• In flipFuses(), the resetAdHocDarwinSignature codesign reset now matches an anchored path segment — (^|[\\/])[^\\/]+\.app([\\/]|$) — so a <name>.app directory is detected as a bundle while names like .app or my.app.win are not.

pathToFuseFile is now exported so the path-resolution logic can be unit-tested directly without downloading Electron binaries.

Tests

Adds test/path-resolution.spec.ts with regression coverage:

• A real .app bundle path and its inner Contents/MacOS/Electron binary path are still resolved to the framework binary (positive cases).
• A Linux path under a .app-named ancestor (#118) and a Windows path under my.app.win (#95) are returned unchanged and not treated as macOS bundles.

Closes #118
Closes #95

#95 is the same root cause (.includes('.app') false-positive at both call sites) and is fixed here.

🤖 Generated with Claude Code

https://claude.ai/code/session_019E2Tyh4thR7TKQqfLcVUXh

---

Generated by Claude Code

[electron-npm-package-publisher]

🎉 This PR is included in version 2.1.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀