- What is misaf/vendra-user used for?
- misaf/vendra-user provides customer and user management for the Vendra Laravel e-commerce platform. It adds authentication, profiles, addresses, and account handling so stores get a ready-made customer layer. It is a subtree split of the Vendra Modules rather than a general-purpose user package.
- How do I install misaf/vendra-user in a Laravel application?
- Install it with Composer using composer require misaf/vendra-user, then follow the package README for service provider registration, configuration publishing, and migrations. Because it is split from the Vendra Modules, confirm whether the parent misaf/vendra package or other Vendra modules are also required. Run migrations only after reviewing them against your existing user tables.
- Which Laravel and PHP versions does misaf/vendra-user support?
- The supplied release metadata does not state exact Laravel and PHP constraints for v1.12.3. Check the package composer.json and README before installing, and test against your application’s Laravel major version, PHP runtime, database driver, and existing auth scaffolding. Treat any minimum version change as a compatibility item to verify in CI.
- Is misaf/vendra-user a standalone package or part of Vendra?
- It is a subtree split of the Vendra Modules, so its releases track the parent misaf/vendra project. That means you should review both the split repository and the main Vendra repository for documentation and changes. It is not positioned as a framework-agnostic or standalone user library outside the Vendra ecosystem.
- What customer features does misaf/vendra-user add to a Laravel store?
- The package covers customer authentication, profiles, addresses, and account handling. These are the core pieces most e-commerce stores need for a customer layer. Verify the exact feature set, routes, and extension points in the README and source for the version you install.
- How do I publish configuration and run migrations for misaf/vendra-user?
- Use the standard Laravel package workflow: publish the package config with vendor:publish, review the published values, then run php artisan migrate. Diff any published migrations and config against your application’s existing user and address tables before applying them. In production, back up data and test migrations in a disposable or staging database first.
- Can I customize the user model, auth guards, or views in misaf/vendra-user?
- Laravel user packages typically expose customization through published config, migrations, model overrides, and auth guard or provider settings, but confirm the actual extension points in the README and source. If your application already has a custom user domain model, map it carefully before enabling the package’s customer layer. Avoid editing vendor files so future Composer updates remain manageable.
- How should I test misaf/vendra-user before using it in production?
- Install it on a branch with pinned Composer constraints, run migrations in a disposable database, and execute your existing auth and account test suite. Add coverage for registration, login, profile updates, address handling, and account deletion or deactivation if supported. Stage the change with production-like data and keep a rollback plan before rollout.
- What changed between v1.11.0 and v1.12.3, and is it safe to upgrade?
- The provided context shows a jump from v1.11.0 to v1.12.3 without itemized release notes, so treat it as an upgrade candidate rather than an automatic update. Retrieve the GitHub compare diff and check for new migrations, config defaults, service-provider bindings, auth guard changes, and dependency updates. Run static analysis, CI, and staging tests, and retain a rollback path to v1.11.0.
- Is misaf/vendra-user actively maintained, and what are the alternatives?
- Maintenance activity and issue-tracker responsiveness are not established by the supplied metadata, so review the GitHub repository and release cadence directly. For alternatives, compare Laravel Breeze, Jetstream, Fortify, and e-commerce customer modules, but choose based on whether you need Vendra-specific integration. If authentication is critical, require a documented changelog and security disclosure process.