Weave Code
Pwa Bundle Laravel Package
nowo-tech/pwa-bundle
A Symfony bundle for adding Progressive Web App capabilities to your site, with configuration for web app manifests, service workers, caching, and installability so users get a fast, app-like experience.
nowo-tech/pwa-bundle is a Symfony bundle for adding Progressive Web App capabilities to your PHP application with minimal configuration. It helps deliver an installable, app-like experience by integrating essential PWA building blocks into your Symfony project.
- Web app manifest support for installability and branding
- Service worker integration for offline-ready behavior
- Configurable caching and asset handling
- Simple Symfony bundle setup and configuration
- Foundation for mobile-friendly, app-like experiences
Frequently asked questions about Pwa Bundle
- Is nowo-tech/pwa-bundle compatible with Laravel?
- No. It is a Symfony bundle, so it relies on a Bundle class registered in config/bundles.php, a DependencyInjection extension that compiles a configuration tree, and services resolved by the full Symfony container. Laravel ships some Symfony components but not the HttpKernel and complete DI stack the bundle lifecycle needs, so nothing in the package will boot. Treat it as a reference implementation for a Laravel port, not as an installable dependency.
- Can I install this Symfony bundle in a Laravel project via Composer?
- Composer will install it at the filesystem level without error, but it will do nothing at runtime. The bundle is never booted, its routes are never registered, and its services are never wired, so you end up with dead code and a misleading entry in composer.json. Anything type-hinting Symfony HttpKernel or DependencyInjection classes will also fail to resolve.
- What features does nowo-tech/pwa-bundle actually provide?
- It adds Progressive Web App capabilities to a Symfony application: a configurable web app manifest, a service worker, an offline fallback page, and a client-side install prompt. The manifest is a JSON document and the service worker is a JavaScript file served from the scope root with the correct Service-Worker-Allowed and cache headers. The most reusable parts are the configuration schema it exposes and its service worker template.
- Does this package support Laravel 10 or Laravel 11?
- There is no Laravel support at all, for any version, because the package has no Laravel service provider, no publishable config, and no Laravel-facing routes. Its compatibility matrix targets PHP and Symfony versions instead. If you need a PWA in Laravel 10 or 11, plan on building or adopting a Laravel-native package rather than installing this one.
- How would I implement a PWA manifest and service worker in Laravel?
- A Laravel-native equivalent is a service provider, a publishable config file, two routes (one returning the manifest JSON, one returning the service worker JavaScript), and a header or middleware step to serve the worker from the scope root with Service-Worker-Allowed and no-cache headers. A Blade view or published static file can handle the install prompt via the beforeinstallprompt event, and an offline fallback route covers network failures. The pieces are small and well understood; the schema you define in config is what carries the actual design work.
- Can I reuse the service worker template from this bundle in Laravel?
- Yes. The service worker is plain JavaScript and framework agnostic, so its caching logic and cache-versioning approach port cleanly. What you must rewrite is the plumbing: the route that serves it, the response headers, and the cache-busting hook tied to your deploy process. Review the template directly in the repository before copying, since the package has no third-party usage feeding back fixes.
- What are the production risks of a service worker, and how should I test one?
- A service worker sits between the user and the network, so a misconfigured cache strategy produces stale assets, white-screen failures on bad deploys, and incidents that survive releases because the old worker still controls the new page load. Always version the cache, ship a kill switch to unregister or force-update, and avoid caching HTML aggressively. Test with DevTools offline mode, in incognito, and against a real deploy where you change assets without changing the worker. This is the highest-risk surface in the package and the part you inherit if you port it.
- How long does it take to port this bundle's functionality to Laravel?
- For a competent Laravel developer, a manifest route plus service worker, headers, and offline fallback is roughly three to seven engineering days. Per-route configurable caching strategies and a proper install prompt flow push it longer. You are mostly buying a configuration schema you will adapt anyway, so budget the time for design and testing rather than code translation.
- Are there Laravel PWA packages I should use instead?
- There are Laravel-native options such as eringee/laravel-pwa and silviolleite/laravelpwa, though you should check their recent commit activity and Laravel version constraints before adopting either. Many teams end up writing the manifest route and service worker themselves because the surface area is small and service worker behaviour needs to match their deploy strategy. Whichever route you take, avoid pulling in a Symfony bundle and expecting it to work.
- Is nowo-tech/pwa-bundle actively maintained and safe to depend on?
- Adoption signals are effectively absent: zero stars, zero dependents, and a single maintainer with no visible contributor base. The recorded last-release date does not match a normal release cadence, so treat the supply-chain metadata as unconfirmed and inspect the repository directly before reusing code. With no field usage and no external review, you should assume you own maintenance from day one, which is another argument for porting the concept rather than depending on the package.
Weaver
How can I help you explore Laravel packages today?