- Is Fibers Rocket compatible with Laravel 10 and PHP 8.2+?
- No, Fibers Rocket was last updated in 2019 and targets Laravel 5.x–7.x. You’ll need to fork and modernize it for Laravel 10+ or PHP 8.2+, as core Artisan commands and Blade syntax have evolved significantly. Test thoroughly in a sandbox before adoption.
- How does `fibers:create` differ from Laravel’s built-in `make:model` or `make:controller`?
- Fibers Rocket generates a full MVC stack (model, controller, migrations, views, routes) in one command, while Laravel’s tools create components individually. It also auto-fills relationships (e.g., foreign keys) and uses context-aware templates, saving time on boilerplate. However, its templates may conflict with newer Laravel features like `@vite` directives.
- Can I customize the generated templates without forking the package?
- Templates are designed to be human-readable and modifiable. Override them by placing custom versions in your project’s `resources/views/vendor/fibers-rocket/` or similar paths. However, since the package is stale, some template logic may break in modern Laravel versions, requiring manual adjustments.
- Will Fibers Rocket work with custom Eloquent models or non-standard database schemas?
- It relies on Laravel’s default Eloquent conventions (e.g., `fillable`, `casts`). If your app uses custom accessors, mutators, or non-standard table structures, the generated migrations or models may need manual fixes. Test with your schema first to avoid surprises.
- Are there alternatives to Fibers Rocket for Laravel 10+ with active maintenance?
- Yes. For scaffolding, consider Laravel’s built-in `make:` commands (now enhanced with `--api`, `--resource` flags) or packages like **laravel-shift** for bulk code generation. For IDE support, **laravel-ide-helper** is actively maintained. For full-stack starter kits, **Laravel Jetstream** or **Breeze** are production-ready alternatives.
- Does Fibers Rocket support testing scaffolding (e.g., creating test classes)?
- No, it focuses on MVC scaffolding only. For tests, use Laravel’s `make:test` or integrate with third-party tools like **pestphp/pest** or **mockery/mockery**. You’d need to manually create test files or extend the package via a fork.
- How do I handle Blade template conflicts with modern Laravel (e.g., `@vite`, `@stack`)?
- The package’s templates use older Blade syntax. Override them in your project and update directives like `@extends('layouts.app')` to `@extends('layouts.main')` or add `@vite` support manually. For a seamless experience, fork the package and update its templates to match Laravel 10’s conventions.
- Is Fibers Rocket safe to use in production, or should it be limited to development?
- It’s designed as a dev-time tool with no runtime overhead, but its stale maintenance raises risks. Use it for prototyping or internal tools where you can manually refine generated code. Avoid relying on it for production-critical scaffolding without thorough testing and customization.
- Can I extend Fibers Rocket to add custom commands or logic?
- The package lacks official extensibility hooks, but you can create custom Artisan commands by copying its structure. Override templates or use service providers to inject logic. However, due to its age, some internal methods may not align with Laravel 10’s architecture, requiring reverse-engineering.
- What’s the best way to evaluate Fibers Rocket before adopting it in a project?
- Start by installing it in a `require-dev` sandbox project (`composer require-dev fibers/rocket`). Test core workflows like `fibers:create`, migration generation, and view scaffolding. Check for conflicts with your Laravel version, CI/CD pipelines, and custom code. Document any manual fixes needed for production use.