- What is perform/dev-bundle used for in Laravel projects?
- Perform Dev Bundle is a Laravel package that aggregates common development-only tooling — debugging, testing and workflow utilities — into a single require-dev install so teams do not have to wire each dependency individually. Its value is standardizing a dev baseline across many repositories rather than adding runtime capability. The README excerpt available here is empty, so inspect the package's composer.json for the exact dependency set before adopting it. Treat it as a convenience and consistency layer, not a feature package.
- How do I install perform/dev-bundle and is it require-dev only?
- Install it with composer require --dev perform/dev-bundle, then run composer update --with-dependencies and review the resolved dependency tree. Because it is a development bundle, it belongs exclusively in require-dev and should contribute nothing to your production autoload surface. Add a CI guard that fails the build if the package appears in the production dependency graph. If Composer prompts about plugin allowances, confirm what plugin is being authorized before approving.
- Which PHP and Laravel versions does perform/dev-bundle support?
- The provided context does not publish a supported PHP or Laravel version matrix, so check the require and require-dev constraints in the package's composer.json before committing. Compare those ranges against the versions your applications run today and plan to run next year. Because a bundle drags in a broad transitive graph, a single constraint mismatch can block resolution for the whole set. Pilot in one low-risk branch rather than rolling out across a monorepo first.
- Is perform/dev-bundle a metapackage or does it include a service provider?
- The available description only calls it a subtree of the Perform Dev Bundle, so this is unverified. Check the type field in composer.json and look for a src directory containing a ServiceProvider or config publish stubs. A pure metapackage has near-zero integration surface; shipping runtime code raises it considerably. Confirm this before evaluating anything else, since it changes both your upgrade and removal strategy.
- Will perform/dev-bundle conflict with PHPStan, Pint, Pest or Rector versions I already pin?
- That depends entirely on whether the bundle pins its transitive dev dependencies or leaves them ranged. Pinned versions give you opaque but stable upgrades; floated versions are transparent but can shift under you. In a branch, add the bundle, remove the now-redundant individual dev dependencies, then run composer update --with-dependencies and diff the resolved tree. Compare lint, static-analysis and test output against your pre-change baseline.
- Does perform/dev-bundle overwrite existing phpstan.neon or pint.json config files?
- This is not stated in the available context, so check whether the bundle ships config publish stubs and whether they are additive or overwrite existing files. Back up or commit your current phpstan.neon, pint.json and similar configs before installing anything. If published configs are then edited locally, repositories silently drift away from bundle defaults. Re-publishing on upgrade should be treated as a deliberate, reviewed diff rather than a routine command.
- Does perform/dev-bundle need a Perform account, license key or private Composer registry?
- The context does not confirm whether this package depends on private Perform packages or an internal Composer registry. Verify by inspecting the repositories, dist URLs and any authentication requirements in composer.json. A private registry dependency breaks reproducibility for external consumers and new-hire onboarding. If authentication is required, document the credentials flow in your onboarding runbook before adopting.
- Can perform/dev-bundle accidentally end up in production dependencies?
- It should not, provided everyone installs it with --dev and no other package requires it in require. Add a CI check that inspects the production lock to fail if the bundle or its runtime-adjacent dependencies appear. This also guards against someone promoting it into require during a refactor. Given a large transitive graph, keeping it out of production is both a hygiene and a supply-chain control.
- How do I remove or eject perform/dev-bundle later?
- Ejecting means inlining the bundle's dependency list and keeping the published configs it generated. Copy the require-dev entries from its composer.json into your own, run composer remove --dev perform/dev-bundle, and confirm your lint, static-analysis and test gates still pass. This should be achievable in an afternoon for a single service. Document the eject path up front so the bundle is never a hard dependency you cannot unwind.
- Is perform/dev-bundle actively maintained and widely adopted?
- There is essentially no external evidence available here: no stars, no dependents, no issue history and no community to surface breakage. Treat every stability claim as unverified and ask the maintainer for a stated support commitment and license terms. If maintenance is goodwill rather than contractual, your team effectively owns the fork when things break. Plan for that contingency before standardizing many repositories on it.