- What is nativephp/php-bin used for?
- nativephp/php-bin provides precompiled PHP runtime binaries for NativePHP desktop applications. It is consumed at build and packaging time so your Laravel app can ship with a bundled PHP runtime instead of depending on a system PHP install. It is not intended for server-rendered Laravel apps, queue workers, or general CLI tooling.
- How do I install nativephp/php-bin in a Laravel project?
- You add it as a Composer dependency in a Laravel application that is being packaged with NativePHP. Integration is typically just a Composer pin, with no application code changes required. NativePHP's packaging pipeline consumes the platform-specific artifacts during the desktop build.
- Which PHP versions does nativephp/php-bin support?
- Version 1.2.0 publishes builds for PHP 8.3, 8.4, and 8.5 across the supported platform matrix. PHP 8.2 is not mentioned in the 1.2.0 changelog, so confirm whether it has been dropped or is simply absent from those notes. PHP 8.5 support is available, but it may be ahead of validation by Laravel, NativePHP core, and third-party packages.
- Does nativephp/php-bin work with Laravel applications?
- Yes, for Laravel applications that are shipped as NativePHP desktop binaries. It does not change how a normal server-rendered Laravel application runs, and it does nothing for hosted SaaS deployments or queue workers. Your Laravel and package compatibility still needs to match the bundled PHP runtime version.
- Do end users need PHP installed to run a NativePHP app with php-bin?
- No, the purpose of nativephp/php-bin is to provide a self-contained PHP runtime bundled with the desktop application. That removes the requirement for a global or system-installed PHP on the user's machine. You still need to handle platform concerns such as signing, notarization, SmartScreen reputation, and OS runtime prerequisites.
- Which platforms are supported by nativephp/php-bin 1.2.0?
- The 1.2.0 build matrix covers Linux arm64 and x64, macOS arm64 and x64, and Windows x64. That is roughly fifteen artifact targets per release, rebuilt together for PHP 8.3, 8.4, and 8.5. Windows arm64 is not listed, and supported OS floors such as macOS version, Windows version, and glibc should be verified before release.
- What changed with macOS binaries in nativephp/php-bin 1.2.0?
- The 1.2.0 notes mention removing unused macOS binaries, which suggests some previously published macOS artifacts are no longer available. If your build scripts reference a specific artifact path or variant, this can break at the packaging step rather than at runtime. Check your pinned artifact references before upgrading.
- Is the sodium extension included in nativephp/php-bin builds?
- Sodium was added to the php-extensions list in version 1.2.0. That is additive and generally low risk, but it changes the runtime contract compared with 1.1.1. Confirm whether sodium is enabled in all platform builds and whether it affects installer size or runtime behavior your app depends on.
- Are nativephp/php-bin binaries signed, checksummed, or reproducible?
- Version 1.2.0 improves provenance visibility through PR-level history and a static-php-cli bump to 2.8.2, indicating a known open-source build toolchain. The release notes do not claim checksummed, signed, or reproducible-verified artifacts. Treat artifact verification as an open question and confirm it before relying on the binaries in production.
- Should I use PHP 8.5 with NativePHP in production?
- PHP 8.5 support in nativephp/php-bin 1.2.0 extends the build matrix, but early adoption is a compatibility bet. Laravel, NativePHP core, and third-party packages may not yet be validated against PHP 8.5. Validate your full stack before choosing it for production, and confirm the recommended production PHP minor with the NativePHP project.