- What fake data does astersnake/faker-chile generate?
- The package adds Chilean fake data to FakerPHP, including RUTs, names, addresses, regions, communes, phone numbers, and companies. It is designed for seeding Laravel applications and building realistic local fixtures in tests. The RUT generator was specifically changed in release 1.0.4.
- How do I install astersnake/faker-chile in a Laravel app?
- Install it as a dev dependency with composer require --dev astersnake/faker-chile. Register the provider with Faker by calling $faker->addProvider(new Astersnake\FakerChile\Provider($faker)) or the package's documented provider class. In Laravel, wire it once in a shared test base class or a service provider used for tests and seeders.
- Does astersnake/faker-chile auto-register with Laravel's fake() helper?
- No, the package is a FakerPHP provider and does not appear to auto-register with Laravel's fake() helper or model factories. You need to add the provider manually through $faker->addProvider(...). Put that registration in one shared test base class so factories and seeders use the same configured Faker instance.
- Which Laravel and PHP versions does astersnake/faker-chile support?
- Release 1.0.4 widens support to Laravel 11 and PHP 8.2 through PHP 8.3, which removes a common blocker for modern applications. Older Laravel 10 or PHP 8.1 projects may need to stay on 1.0.3 unless composer.json constraints were also widened. Check the package's composer.json before bumping a legacy app.
- Is the RUT generated by faker-chile checksum-valid?
- Release 1.0.4 includes a fix titled generate correct RUT, but the supplied context does not confirm whether every generated value passes Chile's checksum algorithm or whether the change is only formatting. If your tests depend on checksum-valid RUTs, add explicit validation assertions instead of assuming the provider guarantees it. Treat the RUT output as a behavior change and verify it in your own test suite.
- Will upgrading to faker-chile 1.0.4 break my snapshot tests?
- It can, because the RUT fix changes generated output and any snapshot, fixture, or assertion that captured an older RUT may now fail or validate stale data. Inventory factories, seeders, database fixtures, and snapshot tests that consume generated RUTs before upgrading. Pin to 1.0.4 deliberately, then refresh or regenerate captured values after the change is reviewed.
- Can I use astersnake/faker-chile in production seeders?
- It is intended as a dev-only dependency for tests and development seeding, so it will not be installed in production when you run composer install --no-dev. If a production deployment genuinely needs Chilean fake data during seeding, install it explicitly rather than relying on the dev dependency. Confirm that build artifacts and composer.lock do not accidentally pull it into runtime images.
- Does faker-chile work with Laravel 10 and PHP 8.1?
- The 1.0.4 release targets Laravel 11 and PHP 8.2 to 8.3, so legacy apps on Laravel 10 or PHP 8.1 may need to remain on 1.0.3. The supplied context does not confirm whether the newer release narrows constraints or simply adds support. Verify the actual composer constraints for your target Laravel and PHP versions before upgrading.
- Are there alternatives to astersnake/faker-chile for Chilean fake data?
- This is a niche package, so maintained forks or other Chilean FakerPHP providers may be limited. Compare Packagist download volume, issue responsiveness, release cadence, and whether a security policy or advisory history exists. If no maintained alternative is available, keep bespoke RUT helpers behind a single interface so you can swap providers later.
- Is astersnake/faker-chile safe to add to my supply chain?
- The package has a single primary maintainer and low visibility, and the supplied data provides no download, star, or CVE signal to confirm supply-chain confidence. Dependabot activity suggests reasonable hygiene, but human bandwidth on the package appears limited. Pin an exact version, review the lockfile diff, and monitor releases before floating to newer versions.