Weave Code
Laravel Pwa Laravel Package
foxws/laravel-pwa
Laravel PWA adds progressive web app support to Laravel apps with manifest and service worker generation, install prompts, icons, and offline caching so users can install your site and use it like a native app.
foxws/laravel-pwa brings Progressive Web App capabilities to your Laravel application with minimal configuration. It generates a dynamic web app manifest and service worker, making your site installable on desktop and mobile while enabling offline support and faster repeat visits.
- Configurable manifest generation (name, icons, theme colors, display mode)
- Service worker scaffolding with cache strategies for assets and pages
- Install prompt and offline fallback support
- Publishable config, views, and assets for full customization
- Blade directives and helpers for quick integration
Frequently asked questions about Laravel Pwa
- How do I install and set up foxws/laravel-pwa in a Laravel app?
- Install it with Composer (composer require foxws/laravel-pwa), then publish the package config and assets. Next you register the manifest and service worker route, and drop the provided Blade directives into your main layout. Setup requires your app to be served over HTTPS (or localhost) with the manifest served at a correct path and Content-Type.
- Which Laravel and PHP versions does foxws/laravel-pwa support?
- A public version matrix is not stated in the available material, and the technical evaluation explicitly lists the supported Laravel/PHP matrix and CI coverage as an open question. Check the composer.json constraints and the repository's CI workflow before committing. The package is evaluated as a good fit for Laravel 10, 11, and 12 Blade or Livewire applications with a Vite build.
- Can I keep my own service worker instead of the one foxws/laravel-pwa generates?
- This is flagged as an open question in the technical evaluation, so confirm it before adopting the package. The package supplies tools for generating manifests and service workers, but browsers allow only one service worker per scope, so any existing service worker registered at or above the same path will collide. If you need a bespoke caching strategy, verify whether you can supply your own implementation while still using the manifest and registration plumbing.
- How do I stop the service worker from serving stale content after a deploy?
- Cache invalidation is the dominant risk with any service worker, and the worst case is a cached HTML shell or hashed asset that leaves users on a white screen after a release. Decide on a versioned service worker plus an explicit purge strategy before rollout, and test the upgrade path with a real deploy rather than only in development. The documented versioning story is one of the key questions the technical evaluation recommends closing before committing.
- Does foxws/laravel-pwa work with Vite?
- Vite is the expected best-fit asset pipeline for this package, since it targets Laravel apps where the service worker does not need a separate Workbox build step. However, asset pipeline support (Vite-first, Mix, or agnostic) and any assumptions about the public or build directory are listed as open questions in the evaluation. Confirm how hashed build assets are handled in your caching strategy.
- How is service worker scope handled for multi-tenant or subdirectory deployments?
- Scope handling for multi-domain, multi-tenant, and subdirectory deployments is an open question that should be verified before adopting the package. Service worker scope is determined by the path the file is served from, so an app hosted under a subdirectory needs a registration path and manifest start_url that match that subdirectory. Test on a staging environment that mirrors your real deployment path.
- Does foxws/laravel-pwa support push notifications or background sync?
- The package is described as manifest, service worker registration, icon and asset plumbing, and install-prompt affordances, with offline caching support. Push notifications and background sync are not described in the available material, so treat it as a manifest plus offline caching tool unless you confirm otherwise in the source. If those features are requirements, plan to extend the service worker yourself or choose a different approach.
- Is foxws/laravel-pwa a good alternative to Workbox?
- It is a good fit if you have a Blade or Livewire monolith and want installability plus offline fallback without adding Workbox as a bespoke frontend build step. It is a poor fit if you already ship a Workbox build or a hand-rolled service worker, since the two will fight over the same scope. For API-only services with native clients, PWA tooling like this adds no value.
- Does foxws/laravel-pwa work with Inertia and Livewire?
- Blade and Livewire applications are the best fit, because the package is Laravel-native config, routes, and Blade directives rather than a separate frontend toolchain. Inertia apps are an acceptable fit, provided the service worker does not fight the client-side router's own caching behaviour. Verify navigation and offline behaviour on a real Inertia build before relying on it.
- Is foxws/laravel-pwa actively maintained and safe for production?
- The project appears to be small or single-maintainer, which the technical evaluation calls acceptable for a bounded, replaceable concern like PWA plumbing but not for an unpinned critical-path dependency. Release cadence, test coverage, and whether there is a security disclosure policy are listed as questions to close. The 2.6.0 release itself is additive and inert at runtime: it adds a Laravel Boost skill and tip (PR #22) that is simply unused if your team does not use Boost.
Weaver
How can I help you explore Laravel packages today?