Weave Code
Larasell Laravel Package
larasell-dev/larasell
Larasell is a Laravel package that adds a lightweight commerce layer to your app: products, carts, checkout, orders, payments, and customer accounts built on Eloquent and Blade, so you can launch a single-vendor store or marketplace without stitching together separate packages.
An e-commerce package built on top of Laravel
Frequently asked questions about Larasell
- How do I install Larasell in a Laravel app?
- Install it with Composer using the package name larasell-dev/larasell, then let Laravel package auto-discovery register the service provider. Publish any config, migrations, and assets that the README documents, run migrations, and create products before testing carts and checkout. Because version 1.19.1 removes the admin panel, pin an exact version during evaluation rather than floating a constraint.
- Which Laravel versions are supported by Larasell?
- The available technical notes only say compatibility with current Laravel is assumed; they do not provide exact version constraints. Treat the package's composer.json and README as the source of truth, then run your test suite on the Laravel version you deploy. If you must stay on 1.19.0 for the admin panel, verify that pinned version against your framework version too.
- Why was the admin panel removed in Larasell 1.19.1?
- The 1.19.1 release is labeled fix: remove admin panel, so a user-facing subsystem was removed in a patch release. The notes give commit 941c143 but no explanation of whether the panel was extracted into another package or deleted outright. Diff v1.19.0 against v1.19.1 and ask the maintainer for the intended replacement before upgrading.
- Is upgrading from Larasell 1.19.0 to 1.19.1 safe?
- It is safe only if your application never relied on the bundled admin panel. If it did, routes, Blade or Livewire views, config keys, and published assets may stop resolving at runtime with 404s or view-not-found errors rather than a clear Composer failure. Pin larasell-dev/larasell to 1.19.0 while you diff the releases and search your codebase for panel references.
- Does Larasell still include an admin panel?
- No, version 1.19.1 removes the admin panel according to the release note. The available notes do not state whether a separate installable package replaces it, so do not assume a drop-in back office exists. Teams that need administration should evaluate Filament, Nova, a custom panel, or confirm a successor package with the maintainer.
- Can Larasell power a single-vendor store or a marketplace?
- Larasell is described as a lightweight commerce layer for a single-vendor store or marketplace, with products, carts, checkout, orders, payments, and customer accounts on Eloquent and Blade. The provided material does not detail multi-vendor scoping, commissions, or vendor payouts, so validate those requirements against the data model and source. Build a small proof of concept for the marketplace flows you need before committing.
- How does Larasell handle checkout, orders, and payments?
- The package provides checkout, order, and payment concepts built on Eloquent models and Blade views, so you can customize the flow in your Laravel app. The exact payment gateways, webhook handling, and order state transitions are not described in the provided notes. Inspect the package config and source, and test payment flows in a sandbox before production.
- How should I configure products and carts in Larasell?
- Configuration is expected to follow standard Laravel package patterns: publish config, run migrations, and define or seed products through Eloquent models. Cart behavior and checkout settings should be adjusted through the package config and overridden views rather than editing vendor files. Confirm the actual config keys and model names in the README or source for version 1.19.1.
- How do I test Larasell before using it in production?
- Pin an exact version and commit composer.lock so CI does not pull 1.19.1 unintentionally. Run migrations against a test database and add feature tests for product listing, cart updates, checkout, order creation, payment callbacks, and customer account access. Also test route and view resolution if you are migrating from 1.19.0, because admin panel removal can fail only at runtime.
- Is Larasell actively maintained enough for production?
- The available assessment notes limited repository metadata and a single release entry, so release cadence and maintainer responsiveness are unknown. A single-maintainer package that removes a subsystem in a patch release carries support risk, so pin versions and review diffs. For production, confirm the maintainer's versioning plans, and compare alternatives such as Lunar or Aimeos if long-term support is critical.
Weaver
How can I help you explore Laravel packages today?