Weave Code
Electron Laravel Package
nativephp/electron
NativePHP for Electron lets Laravel developers build and ship native desktop applications from a single PHP codebase. It bundles a PHP runtime with Electron to create cross-platform Windows, macOS, and Linux apps using familiar Laravel tools—no separate desktop stack required.
Electron backend for NativePHP
Frequently asked questions about Electron
- What is nativephp/electron and how does it work with Laravel?
- It is the Electron runtime and bridge for NativePHP that lets a Laravel application run as a native desktop app. It bundles a PHP runtime, serves the Laravel app from a local HTTP listener, and wraps it in an Electron shell while handling process orchestration, IPC, windows, menus, dialogs, notifications, and tray integrations.
- How do I install NativePHP for Electron in a Laravel application?
- The standard path is to add the nativephp/electron Composer dependency and run the NativePHP Artisan commands such as native:install, native:serve, and native:build. A Node toolchain is required on the build machine or CI runner, so validate the documented setup steps before wiring it into an existing pipeline.
- What are the build requirements for a NativePHP desktop app?
- You need a Laravel app, the package's Composer dependencies, and a Node toolchain on the machine or CI runner that produces the desktop build. Packaging uses Electron tooling, so your CI should also account for platform-specific signing, notarization, and installer generation; confirm exact versions and prerequisites in the official docs.
- Which Laravel and PHP versions are supported by nativephp/electron?
- The supplied overview and 1.3.0 changelog do not pin specific Laravel or PHP version ranges, so do not assume compatibility from those notes alone. Check the package's composer.json constraints and the NativePHP documentation for the supported Laravel, PHP, and Electron versions before adopting it.
- Does nativephp/electron support macOS, Windows, and Linux builds?
- Yes. The package provides cross-platform builds for macOS, Windows, and Linux and is described as packaging-ready for distributing desktop apps. You should still run a full build and install test on each target platform because installer formats, signing, and notarization differ.
- How does the PHP to Electron bridge work and is IPC secure?
- The package provides a secure PHP–Electron bridge for IPC and process management, with the Laravel app served locally and managed by the Electron runtime. The overview presents this as a first-class integration, but security review should include the navigation guard, external-content handling, and how the local listener is exposed. Validate the bridge details against the source and docs for your threat model.
- What does the navigation guard in 1.3.0 do and can it break OAuth redirects?
- PR #250 adds a navigation guard that can prevent the Electron shell from navigating to external content and intercept in-app routing. The changelog does not confirm whether it is default-on, default-off, or breaking for existing window.open and OAuth redirect flows. Spike third-party OAuth callbacks, payment redirects, and external link-out before relying on it.
- How does the Windows port-conflict fix affect localhost ports and multiple app instances?
- The 1.3.0 Windows port-conflict fix implies the local server binding strategy changed to tolerate concurrent instances. Any code that hardcodes or assumes a fixed localhost port, including webhooks, deep links, or local API callbacks, must be re-verified. Test multiple simultaneous app instances and confirm how the chosen port is discovered.
- What changed with publisher config and the auto-updater in 1.3.0?
- PR #243 is a defect fix: publisher configuration is only consumed when the updater is enabled, so apps that do not ship an auto-updater should see fewer build-time failures. This improves first-integration success, but auto-update metadata generation still needs testing for apps that do enable the updater. Confirm your publisher settings and update channel behavior in a staging build.
- What are the biggest production risks in nativephp/electron 1.3.0?
- The highest-signal risk is the electron-builder downgrade in PR #251, which can affect installer formats, code signing, macOS notarization, and auto-update metadata; ask maintainers for the rationale and run a full build-matrix regression. Also verify the navigation guard defaults, port binding changes, and which Electron major ships with 1.3.0, since Electron shells that lag Chromium security patches are a standing exposure. The release also comes from a small contributor set, so review depth and maintenance cadence are worth assessing.
Weaver
How can I help you explore Laravel packages today?