Weave Code
Dummy Laravel Package
directorytree/dummy
A Laravel package from DirectoryTree for generating and managing dummy data, making it easy to scaffold placeholder records and test content during development. A lightweight helper for faster prototyping, seeding, and testing in your Laravel apps.
directorytree/dummy is a lightweight Laravel/PHP package for scaffolding placeholder dummy data and stub classes, making it easy to wire up prototypes, seeders, and test fixtures without boilerplate. Drop it into a DirectoryTree-based project to generate consistent, disposable records and models during development.
- Generates dummy models and records for rapid prototyping
- Seamless Laravel integration via service provider and config
- Ideal for seeders, tests, and UI mockups
- Simple, dependency-light API that stays out of your way
Frequently asked questions about Dummy
- What is directorytree/dummy used for in Laravel?
- DirectoryTree Dummy is a Laravel package for quickly generating realistic dummy data for Eloquent models and database tables. It is intended to simplify seeding development, QA, and testing environments with less fixture boilerplate. Treat it as a require-dev test-data utility rather than a production runtime dependency.
- How do I install directorytree/dummy?
- Install it as a Composer dev dependency and pin it to ^2.0.1 for current compatibility. Run composer require --dev directorytree/dummy:^2.0.1 in your Laravel project. Keep it in require-dev and avoid adding it to production requirements.
- Which Laravel versions does directorytree/dummy support?
- Recent releases explicitly track Laravel 12 and 13, and v1.1.0 removed the hard Laravel framework dependency. Laravel 11 through 13 is the best-fit range, while versions below 11 should be treated cautiously. Laravel idioms remain central, so non-Laravel use is only partial.
- Is directorytree/dummy a production dependency?
- No, it is a require-dev test-data utility for development, testing, QA, and CI environments. It should not be installed in production require blocks. Use it to generate dummy data for Eloquent models, seeders, and test fixtures.
- Does directorytree/dummy work with PHPUnit and Pest?
- Pest support appears native per the package dev dependencies, and PHPUnit may work for general usage. Laravel-specific integration in package tests may need Testbench. Teams should pilot the package with their chosen test framework before standardizing.
- What are the risks of using directorytree/dummy?
- The main risks are low public adoption, sparse documentation, and single-maintainer concentration, not runtime complexity. The v2.0.0 breaking rename and v2.0.1 edge-case fix show API stability still needs watching. Pilot it in one test suite, pin versions, and keep native factories, Faker, or an internal wrapper as a fallback.
- Can I use directorytree/dummy outside Laravel?
- Non-Laravel use is partial because the package still assumes Laravel conventions such as HasFactory, Arr helpers, and factory semantics. Treat non-Laravel support as experimental unless your team accepts adapters for Laravel-style factory behavior. It is not a drop-in replacement for general PHP data generation.
- How does directorytree/dummy compare to Laravel native factories?
- It is best viewed as an augmentation that reduces repetitive fixture boilerplate, not an automatic replacement for stable native factories. Pilot it where dynamic factory states or factory attribute expansion materially reduce setup code. Do not rewrite factories that already work well with Laravel's native tooling.
- How should I roll out directorytree/dummy in a team?
- Start by inventorying existing factories, seeders, and fixtures, then approve it as a dev-only dependency pinned to ^2.0.1. Pilot one or two non-critical factories behind an internal test helper and compare against native Laravel factory usage. Expand only if metrics show faster fixture authoring, lower flake rate, or clear developer-experience gains.
- What is the upgrade and maintenance plan for directorytree/dummy?
- Pin versions, review release notes, test against supported Laravel versions, and watch for breaking changes such as the v2 class and method renames. Assign an internal owner to document patterns, collect examples, and define escalation paths. Given low adoption and single-maintainer risk, be prepared to wrap or fork the package if upstream maintenance slows.
Weaver
How can I help you explore Laravel packages today?