Weave Code
Laravel Appleseed Laravel Package
genealabs/laravel-appleseed
Laravel Appleseed generates Laravel database seeders from your existing database data. It inspects your tables and creates ready-to-run seeder classes, making it easy to reproduce development or testing environments with familiar artisan db:seed workflows.
Prevent the pesky missing-favicon error log entries, and return 404 if they don't exist.
Frequently asked questions about Laravel Appleseed
- Is laravel-appleseed a database seeder or a favicon 404 handler?
- The package metadata is inconsistent. The overview and blurb describe a Faker-backed database seeding tool with Artisan scaffolding, while the release notes, repository name, and TPM assessment indicate it may be a favicon 404 handler. Confirm the actual Packagist artifact at v0.2.1 before scoping any work. The TPM assessment recommends resolving this ambiguity as the first step.
- What is genealabs/laravel-appleseed used for?
- According to its overview, it streamlines Laravel database seeding by letting you define records declaratively and integrates with Artisan db:seed. The blurb says it generates seeders from existing database data. However, the TPM assessment flags that other metadata describes a favicon 404 handler, so verify the actual package behavior on Packagist.
- Is laravel-appleseed compatible with Laravel 8, 9, 10, or 11?
- No, the last release was on 2015-11-17, targeting Laravel 5.0/5.1. Composer constraints likely pin illuminate/* to ~5.0 and will fail to resolve against Laravel 8–11 without an explicit override. There is no extra.laravel block, so auto-discovery will not work, and manual provider registration is required. The TPM assessment rates integration feasibility on a current stack as low.
- How do I install laravel-appleseed via Composer?
- You would typically run composer require genealabs/laravel-appleseed, but given the package's age, you may need to add version and stability flags. The TPM assessment warns that Composer may fail to resolve dependencies on modern Laravel versions. For legacy Laravel 5.x projects, manual registration in config/app.php is necessary.
- Does laravel-appleseed support Laravel package auto-discovery?
- No, the package lacks an extra.laravel block in its composer.json, so auto-discovery (introduced in Laravel 5.5) will not register its service provider. You must manually add the provider to the providers array in config/app.php. This is consistent with its 2015 release date, which predates auto-discovery.
- Is laravel-appleseed actively maintained?
- No, the last release was in November 2015, and the TPM assessment notes it has 30 stars and zero dependents. There is no public evidence of recent maintenance or testing on modern Laravel versions. The assessment concludes the artifact was abandoned before Laravel 5.5 shipped.
- Can laravel-appleseed generate seeders from an existing database?
- The blurb claims it inspects your tables and creates ready-to-run seeder classes, but the TPM assessment questions whether this is the actual behavior. Due to inconsistent metadata, you should verify this functionality on the real Packagist artifact. If true, it would be useful for reproducing dev or test environments.
- Does laravel-appleseed integrate with Artisan db:seed?
- The overview states it integrates with Laravel's Artisan db:seed workflow, but this claim is under scrutiny. The TPM assessment found conflicting descriptions and rates integration feasibility as low on current stacks. Test the package in a legacy environment before relying on it.
- What are alternatives to laravel-appleseed for Laravel database seeding?
- For modern Laravel, consider native seeders with Faker, or packages like orangehill/buy-now-seeder or laravel/sail. The TPM assessment recommends adopting the pattern rather than the dependency, as the behavior is only ~20–30 lines of native Laravel. For favicon 404 handling, a static asset or server rule is simpler.
- What are the production risks of using laravel-appleseed?
- The TPM assessment notes a small blast radius but non-trivial silent-failure modes, such as route shadowing or the provider quietly failing after a framework upgrade. These are manageable only if you own the implementation and can write tests. The verdict is to not adopt it as a dependency; adopt the pattern natively instead.
Weaver
How can I help you explore Laravel packages today?