- How do I install jeffersongoncalves/laravel-fake-cartoons?
- Install it with Composer using composer require jeffersongoncalves/laravel-fake-cartoons, ideally with the --dev flag because fake data generation belongs in development and testing environments. Laravel's package auto-discovery registers the service provider, so no manual entry in config/app.php is normally needed. Check the README for any optional publishable assets and commit only what your team actually needs.
- Which Laravel and PHP versions does laravel-fake-cartoons 2.0.0 support?
- Version 2.0.0 requires laravel/framework ^12.61.1 or ^13.12.0, and Laravel 11 has been removed from the supported matrix. Laravel 12 requires PHP 8.2 or newer, and Laravel 13 raises that floor further, so verify your runtime image before bumping. Composer will hard-block the update on any application still pinned to an older framework branch.
- How do I generate fake cartoon company names with Faker in Laravel?
- Once installed, the package's Faker provider is reachable through Laravel's fake() helper and the underlying Faker generator, so you can call it inside seeders, factories and tests. It returns fictional company names inspired by well-known cartoons and animated series, which makes seeded records look recognizable in demos. Use it anywhere you would normally call Faker's built-in company formatter.
- Can I seed my database with cartoon characters and avatars using this package?
- Yes. The package ships Faker providers plus seeders for cartoon characters, avatars and related test records, which is exactly the demo, prototyping and database-population use case it targets. Run those seeders in local, staging and CI environments only, and avoid pointing them at production data. If you need records attached to your own domain models, wrap the generated values in your application's model factories.
- Why does laravel-fake-cartoons 2.0.0 require a newer Laravel framework?
- Release 2.0.0 pins laravel/framework to ^12.61.1|^13.12.0 to close two published advisories in the framework itself: GHSA-crmm-hgp2-wgrp, a temporary signed URL path confusion issue, and GHSA-5vg9-5847-vvmq, a CRLF injection in the default email validation rule. Because both fixes live in the framework, the package cannot offer a Laravel 11 escape hatch without shipping a known-vulnerable dependency graph. The constraint bump is therefore a security requirement rather than a cosmetic version change.
- How do I upgrade laravel-fake-cartoons from 1.x to 2.0.0?
- Bump laravel/framework to at least 12.61.1 (or 13.12.0) first, run your test suite, then raise the package constraint to ^2.0 and update. Treat both steps as a single change set so the window where you carry the advisories stays short. Pay close attention to tests covering temporary signed URLs and the default email validation rule, since those are the behaviours the underlying fixes can change. Applications on Laravel 11 have no in-place path and need a scoped framework upgrade project.
- Is laravel-fake-cartoons safe to use in production?
- The package only generates fake data, so it belongs in require-dev and should not be loaded in production. The production-relevant detail is transitive: 2.0.0 asserts a framework floor of Laravel 12.61.1 or 13.12.0, which becomes the effective minimum for every application depending on it. Keep it out of your production autoload path and review its constraint whenever you plan a framework upgrade.
- Does laravel-fake-cartoons work with PHPUnit, Pest and model factories?
- Yes. The Faker providers are ordinary Faker formatters, so they can be called from Laravel model factories, database seeders, PHPUnit tests and Pest tests alike. That makes it straightforward to build fixtures where companies, characters and avatars are generated deterministically per test run. If you need reproducible data, seed Faker with a fixed value in your test setup.
- What are the alternatives to laravel-fake-cartoons for fake data in Laravel?
- The obvious baseline is FakerPHP's built-in company provider, which already ships with Laravel and needs no extra dependency. The reason to pick this package is the specific cartoon-flavoured dataset: fictional company names, characters and avatars tied to popular animated series. If you only need generic company names, plain Faker is lighter and avoids the extra framework constraint.
- Will adding laravel-fake-cartoons 2.0.0 force a framework upgrade across my application?
- Yes, transitively. Adopting 2.0.0 propagates the requirement for Laravel 12.61.1+ or 13.12.0+ to every consumer, so a routine dependency bump becomes a coordinated migration for teams still on Laravel 11. When planning the move, also confirm that your other vendor packages have releases compatible with the Laravel branch you choose, because ecosystem readiness for Laravel 13 can lag behind the framework itself.