Weave Code
Dystore Laravel Package
dystcz/dystore
Dystore is a Laravel/PHP e-commerce package that provides a flexible foundation for building online stores, with tools for product, cart, and order management and an extendable architecture suited to custom storefronts and commerce features.
Collection of ecommerce packages built on top of Lunar and Laravel JSON:API.
Frequently asked questions about Dystore
- What is Dystore and what does it add to Laravel?
- Dystore is a Laravel/PHP e-commerce package built on top of Lunar and Laravel JSON:API. It provides product, cart, and order management plus an extendable architecture for custom storefronts and commerce features. It fits Laravel commerce apps that have already chosen Lunar as the commerce core.
- How do I install Dystore in a Laravel application?
- Install it with Composer using dystcz/dystore, then follow Laravel package conventions: the service provider is auto-discovered, and config and migrations are publishable. Publish assets and run migrations. For 1.0.15, plan on PHP 8.3+ and Laravel 12.x, and run composer why-not before upgrading an existing app.
- Which Laravel and PHP versions does Dystore support?
- The 1.0.15 release dropped Laravel 11 and PHP 8.2 support, so it targets PHP 8.3+ and Laravel 12.x. The provided assessment does not state exactly which PHP 8.3 and 8.4 minors are tested in CI. Check the package constraints and CI matrix before adopting it.
- Is Dystore stable enough for production commerce?
- Treat 1.0.x as potentially breaking: 1.0.15 removed platform support in a patch-level release. Pin exact versions and commit the lockfile instead of relying on ^1.0. Also note that Dystore is pinned to Lunar 1.5.0-beta.6, a pre-release dependency for the commerce data layer.
- How does Dystore handle products, carts, and orders?
- Dystore layers e-commerce features on Lunar and exposes them through Laravel JSON:API. The 1.0.15 release adds product and variant availability scopes plus nested collection-group filters on products. These query-layer additions become contracts that downstream code and API consumers may build on.
- Does Dystore include authentication endpoints such as account-exists and passwordless registration?
- Yes. Dystore 1.0.15 adds a GET account-exists check, a DELETE user endpoint, and registration without a password. The account-exists endpoint is a classic user-enumeration vector unless it is rate-limited and returns generic responses. These changes widen the package into security-sensitive identity flows.
- How are reviews linked to orders in Dystore?
- In 1.0.15, reviews now relate to orders, which implies a nullable foreign key, a migration, and a backfill strategy. Existing reviews will have no order relation, and the change may affect how reviews are attributed, displayed, and exposed in API payloads. The Filament reviews listing also stops applying PublishedScope, so unpublished reviews become visible to admins.
- What are the risks of Dystore depending on Lunar 1.5.0-beta.6?
- Pinning to Lunar 1.5.0-beta.6 puts a production commerce data layer on a pre-release upstream dependency. Schema and behavior churn in Lunar is outside Dystore's control. Ask for the Lunar 1.5 GA timeline and whether beta.6 is API-frozen, and pin versions tightly.
- How should I handle the DELETE user endpoint in Dystore?
- The assessment does not state whether Dystore's DELETE user endpoint performs a soft or hard delete. Define whether order and invoice history must be retained for tax and accounting, anonymize reviews now linked to orders, and verify cascade behavior across Lunar tables. Treat this as an explicit data-retention policy before exposing the endpoint.
- Should I use Dystore for accounts if I already use Laravel auth?
- Dystore's new registration and account endpoints overlap with Breeze, Jetstream, Fortify, SSO, and external identity providers. The package is drifting from a store domain module toward a storefront plus customer account backend. Choose one owner for identity flows and avoid running parallel account lifecycles.
Weaver
How can I help you explore Laravel packages today?