Weave Code
Framework Laravel Package
aurexengine/framework
Custom Chassis Framework (aurexengine/framework) is a Laravel/PHP framework package providing a chassis-style foundation for building applications and modules. Intended as a base layer for project structure, shared conventions, and core utilities.
At a glance
Frequently asked questions about Framework
- What’s the best use case for AurexEngine Framework in a Laravel project?
- AurexEngine shines for projects needing a standardized foundation—like admin panels, modular SaaS backends, or domain-specific apps—where you want consistent structure without Laravel’s full overhead. It’s ideal if you’re building reusable components or shared services across multiple Laravel apps. Avoid it for highly customized auth systems or non-Eloquent databases.
- How do I install AurexEngine in a Laravel 9+ project?
- Run `composer require aurexengine/framework` in your project root. The package assumes Laravel 9+ via composer constraints, but verify compatibility by checking its `composer.json` for exact Laravel version pins. No additional Laravel service provider registration is needed unless the package introduces custom bootstrapping.
- Does AurexEngine replace Laravel’s core components like Auth or Request?
- No, AurexEngine is designed to *extend* Laravel, not replace it. It provides a chassis layer for organizing services and modules while relying on Laravel’s built-in Auth, Request, and Response systems. However, if you’re using custom auth guards or middleware, conflicts may arise—always test thoroughly.
- Can I use AurexEngine with Livewire, Inertia.js, or API Resources?
- Yes, AurexEngine is frontend-agnostic and should work alongside Livewire, Inertia.js, or API Resources since it doesn’t impose frontend dependencies. However, if the package introduces global middleware or route macros, ensure they don’t interfere with your frontend stack’s routing or request handling.
- What Laravel versions does AurexEngine officially support?
- The package claims compatibility with Laravel 9+ via composer constraints, but lacks explicit version testing (e.g., CI badges or Laravel-specific tests). To mitigate risks, pin to an exact Laravel version in your `composer.json` (e.g., `^9.0` or `^10.0`). Check the repo’s issue tracker for reported breaking changes.
- How does AurexEngine handle multi-tenancy or environment-specific configs?
- AurexEngine doesn’t explicitly document multi-tenancy support, so assume it relies on Laravel’s native environment configs (`.env`) and service container bindings. For multi-tenancy, you’ll likely need to extend its service providers or use packages like `stancl/tenancy` alongside it. Always test environment-specific logic in staging.
- Are there alternatives to AurexEngine for Laravel project scaffolding?
- For lightweight scaffolding, consider Laravel’s built-in `make:controller`, `make:model`, or packages like `laravel-shift/blueprint` for CRUD. For admin panels, Filament or Nova offer more polish. If you need modularity, explore `spatie/laravel-package-tools` for package development. AurexEngine is unique in its chassis-style approach but carries higher risk due to lack of documentation.
- Does AurexEngine add performance overhead to Laravel apps?
- The package is designed to be slim, but abstraction layers (e.g., custom service containers or middleware) could introduce minor overhead. Benchmark your app before/after integration, especially for performance-critical routes. If latency is a concern, avoid features like automatic model observers or global middleware.
- How do I test AurexEngine in a Laravel project before full adoption?
- Start with a proof-of-concept: isolate a non-critical module (e.g., a reporting dashboard) and integrate AurexEngine there. Use feature flags to toggle its functionality and monitor for side effects like unexpected middleware or route conflicts. Gradually migrate core features after validating stability.
- What’s the deprecation policy for Laravel version support in AurexEngine?
- The package doesn’t explicitly state a deprecation policy, but it follows Laravel’s minor version constraints (e.g., Laravel 9+). Monitor the repo for updates or reach out to maintainers for long-term roadmap details. If you’re on Laravel 10+, pin to a specific minor version (e.g., `^10.0`) to avoid surprises.
Weaver
How can I help you explore Laravel packages today?