- What is alexlisenkov/laravel-web-push used for?
- It is a Laravel package for sending browser Web Push notifications from a Laravel application. It helps with VAPID key setup, managing user push subscriptions, and delivering messages through a Laravel notification channel. Use it when you need browser push notifications without building the Web Push plumbing yourself.
- How do I install laravel-web-push in a Laravel app?
- Install it as a Composer package in your Laravel project and follow the package configuration steps for VAPID keys and subscriptions. For version 1.1.0, confirm your app runs on a supported PHP 8.x runtime and Laravel 8 constraints before Composer resolution. Test dependency resolution with composer why-not if other packages pin Laravel or PHP versions.
- Does laravel-web-push support Laravel 9, 10, or 11?
- The provided release context confirms improved compatibility for Laravel 8 and PHP 8, but it does not state support for Laravel 9, 10, or 11. Treat newer Laravel versions as unverified until you check the package Composer constraints and changelog. Validate in staging before adopting it on newer Laravel applications.
- Which PHP versions are supported by laravel-web-push 1.1.0?
- Version 1.1.0 improves PHP 8 compatibility and explicitly drops PHP 7.1 and 7.2 support. The exact tested PHP 8 minor versions are not stated, so confirm your PHP 8.x version against the package constraints and CI matrix. Applications on PHP 7.1 or 7.2 must stay on an older package version or upgrade PHP first.
- Is upgrading to laravel-web-push 1.1.0 a breaking change?
- Yes, treat it as a platform-breaking update for legacy environments because PHP 7.1 and 7.2 support is removed and Laravel 8 dependency constraints are upgraded. This is a breaking platform change released under a minor version number. Check Composer resolution and runtime compatibility before rolling it out to production.
- How do I test laravel-web-push before production?
- Adopt 1.1.0 in staging first and run your application test suite plus package-specific integration tests for subscription storage and notification delivery. Use Composer dependency checks such as composer why-not to catch Laravel or PHP constraint conflicts. Keep the previous package version pinned as a rollback until the canary production service is stable.
- What are the production risks of using laravel-web-push?
- Primary risks include Composer dependency conflicts, runtime errors on untested PHP 8 minors, Laravel 8-era dependency deprecation exposure, and legacy apps attempting an unsupported PHP jump. GitHub Actions CI improves confidence but does not prove production compatibility by itself. Roll out gradually and monitor notification delivery and subscription behavior.
- Is laravel-web-push actively maintained?
- GitHub Actions is a positive operational signal because it formalizes CI and reduces manual verification. However, the maintainer support policy and full PHP and Laravel support matrix should be documented before broad adoption. Confirm current maintenance activity and compatibility claims directly from the repository.
- How does laravel-web-push handle VAPID keys and push subscriptions?
- The package is designed to simplify VAPID key setup and manage user push subscriptions. It also provides a Laravel notification channel for delivering Web Push messages to modern browsers. You still need to configure keys and store subscriptions according to the package documentation.
- What should I check before choosing laravel-web-push over alternatives?
- Confirm that its Laravel and PHP support matrix matches your application, especially if you are on Laravel 8, PHP 8, or newer Laravel versions. Review the maintainer upgrade notes, CI matrix, and dependency constraints because the exact tested PHP 8 minors and Laravel range are not stated in the release context. Compare that support policy with alternatives before adopting it across many services.