Weave Code
Pwa Laravel Package
bagisto/pwa
Bagisto PWA adds a progressive web app storefront to Bagisto e-commerce, delivering installable, offline-capable, app-like shopping with fast load times and a native feel on mobile and desktop.
Progressive Web Application transforms your website to a mobile application
Frequently asked questions about Pwa
- How do I install bagisto/pwa in a Laravel Bagisto store?
- Install the module with Composer as bagisto/pwa, register its service provider, and publish the package assets and configuration so the web app manifest and service worker land in your public storefront. Then hook the PWA behavior into your existing Bagisto theme and clear compiled views and caches. Because it is an additive first-party Webkul module, it augments your current Laravel and Bagisto rendering path rather than introducing a separate app stack. Check the package README for the exact artisan publish commands and tags for your release.
- Which Bagisto and Laravel versions does bagisto/pwa support?
- Release v1.3.2 states it is compatible with Bagisto core v1.3.0, so the module rides the core release train rather than versioning independently. That means your upgrade planning should treat the PWA module as part of a Bagisto core upgrade milestone, not a standalone dependency. Confirm the Laravel constraint in the package composer.json for your target Bagisto release before committing.
- Is the Bagisto v1.3.0 dependency enforced in composer.json or only documented?
- The release notes state compatibility with Bagisto v1.3.0, but they do not establish whether that constraint is enforced in composer.json or merely documented. Inspect the package composer.json and your root constraints to see whether Composer will protect you from an incompatible core. If the dependency is only documented, you own the pinning and the upgrade gate.
- Will removing ProductRepository in bagisto/pwa break my storefront?
- PR #165 removes ProductRepository and labels it irrelevant, but any local override, decorator, or extension that references that class will break at load time. Treat the removal as breaking until you have proven otherwise in your codebase. Search your app and custom modules for ProductRepository references early, because this is the highest-probability and cheapest-to-detect integration failure.
- Does the Bagisto PWA service worker cache catalog or price HTML?
- A service worker that caches catalog or price HTML creates a pricing-accuracy failure mode that is a revenue and trust problem, not just a caching nuisance. Review the service-worker strategy in the published assets and explicitly exclude price, cart, and other dynamic commerce responses where accuracy matters. Test stale-cache behavior on mobile and desktop before production rollout.
- What happens if the bagisto/pwa module is disabled or misconfigured?
- PR #202 adds a module status check, which is a real safety improvement because a misregistered or disabled module becomes detectable instead of silently serving a stale service worker. However, it also establishes a state where the storefront runs correctly while PWA features are quietly off. The package surfaces that state but does not alert on it, so you own the monitoring and detectability requirement.
- Is Compare Products state stored server-side or client-side in bagisto/pwa?
- Compare Products is a net-new user-facing surface shipped in v1.3.2 via PR #196, and the release notes do not state whether the comparison state is client-only or persisted in session or the database. Verify the persistence model before relying on it, and confirm whether it interacts with the cart, catalog cache, or price resolution. This matters for cross-device behavior and for cache correctness.
- Is bagisto/pwa production ready or should I wait?
- Treat bagisto/pwa as early adopter territory: it has zero recorded dependents and a 0.3 overall score, so there is no downstream cohort to absorb discovery cost. Contributor concentration also matters, because three of six merged PRs came from first-time contributors, including the Compare Products and module status changes. It is viable if you are committed to Bagisto and willing to co-schedule the module inside your core upgrade milestone with budget for discovery.
- How do I upgrade bagisto/pwa from v1.2.0 to v1.3.2?
- The changelog jumps from v1.2.0 to v1.3.2, so reconstruct v1.3.0 and v1.3.1 from git history before you scope the upgrade honestly. Do not let the patch label drive your change-advisory or CAB classification, because v1.3.2 ships a net-new user-facing surface plus a core compatibility bump. Expect migrations, config republications, asset republication, and cache-clearing steps, and test the service worker and storefront shell after upgrading.
- What are the alternatives to bagisto/pwa for a mobile storefront?
- Bagisto PWA is an additive first-party module that layers installability, a service worker, and an offline-friendly storefront shell onto your existing Bagisto storefront. Alternatives include a native mobile app or a headless frontend, but those introduce a parallel app stack, a second auth system, and a second deploy pipeline. If you are already committed to Bagisto, the PWA module is the least invasive path; otherwise evaluate headless or native against your team and maintenance model.
Weaver
How can I help you explore Laravel packages today?