- How do I install Laravel Structure Kit in my Laravel project?
- Run `composer require mehedi250/laravel-structure-kit` in your project directory. The package integrates automatically with Laravel’s service provider system. No additional configuration is needed unless you want to customize paths or templates.
- Does Laravel Structure Kit support Laravel 13?
- Yes, the package is compatible with Laravel 10–13. It leverages Laravel’s native features like Eloquent, API Resources, and Policies, ensuring seamless integration with the latest versions. Always pin to a specific version (e.g., `^0.1.5`) for stability.
- Can I customize the folder structure it generates?
- Yes, you can define custom paths via configuration. The package allows you to override default locations (e.g., `app/Models/` to `app/Domain/User/`). However, hardcoded templates may require manual adjustments for highly opinionated structures like DDD.
- Will this package work with my existing Laravel project that has non-standard folder layouts?
- It depends. If your project uses unconventional layouts (e.g., `app/Modules/`), you’ll need to either customize paths in the config or manually adjust generated files post-scaffold. The package assumes Laravel’s default conventions by default.
- Does Laravel Structure Kit generate database migrations?
- Yes, it generates migration files, but you’ll need to manually name them (e.g., `create_users_table`). The package doesn’t auto-link migrations to models, so you’ll have to define the relationship in your model’s `$table` property.
- Can I use this package in CI/CD pipelines?
- Yes, the CLI supports automation. Use flags like `--dry-run` to validate scaffolding without writing files, or integrate it into pipelines to generate structures for new features. Avoid generating migrations in CI to speed up builds.
- Does Laravel Structure Kit support testing frameworks like Pest or PHPUnit?
- Yes, the generated stubs are PSR-compliant and integrate with Laravel’s testing tools. You’ll need to manually write test cases, but the structure (e.g., `tests/Feature/`) aligns with Laravel’s testing conventions.
- Is there a way to extend or modify the generated templates?
- Currently, there are no hooks or plugins to extend templates directly. You can fork the package and customize the source or manually override generated files post-scaffold. For complex needs, consider using it as a base and extending it manually.
- How does the UI compare to the CLI for generating structures?
- The UI is ideal for ad-hoc generation with a visual preview, while the CLI is better for automation (e.g., CI/CD). The CLI may offer more flags or options over time, so prefer it for scripts and the UI for interactive use.
- Are there any alternatives to Laravel Structure Kit for scaffolding Laravel projects?
- Yes, alternatives include Laravel Breeze (for auth scaffolding), Laravel Jetstream (full-stack scaffolding), and custom scripts using Laravel’s `make:model` or `make:controller`. Structure Kit stands out for its focus on clean architecture (Service/Repository patterns) and dual UI/CLI approach.