- How do I install alebatistella/duskapiconf in a Laravel project?
- Install it as a dev dependency with composer require --dev alebatistella/duskapiconf. It is intended only for Dusk API test environments, so keep it out of production require. Check the package's composer.json for exact PHP and Laravel constraints before locking it in.
- What is alebatistella/duskapiconf used for in Laravel Dusk API testing?
- It provides configuration helpers for Laravel Dusk suites that focus on API and HTTP assertions. The package aims to reduce environment and test bootstrap boilerplate so API test configuration stays consistent and reusable. It is a dev-only utility and should not affect production architecture.
- Does alebatistella/duskapiconf support Laravel 11 and Laravel 12?
- The only release noted in the assessment is from August 2023, which predates Laravel 11's streamlined skeleton. Auto-discovery may still work, but Laravel 11 and 12 compatibility is not confirmed in the provided context. Prove it on your exact PHP and Laravel matrix with a short spike before adopting.
- Is alebatistella/duskapiconf safe to install in production?
- No. This is a Dusk test helper and should live in require-dev, never in production images. If the package exposes any config-mutation route, the assessment treats environment gating and auth as a hard gate rather than an optional extra.
- How does alebatistella/duskapiconf change configuration during Dusk tests?
- The overview describes configuration helpers for Dusk API test environments, but the provided context does not document the exact persistence mechanism. The TPM assessment warns that a live change only survives across Dusk browser requests if it is written to a file, cache, or database the app re-reads at boot. Inspect the source and confirm the mechanism before relying on it.
- Does alebatistella/duskapiconf work with php artisan config:cache?
- Laravel config caching can silently ignore or nullify runtime config changes, so this must be tested rather than assumed. The provided assessment lists config:cache survival as an open question. Add an explicit CI check if your Dusk flow runs config:cache.
- What are alternatives to alebatistella/duskapiconf for Laravel Dusk config?
- First-party options include Config::set in test bootstrap or per-test setup, Dusk environment files such as .env.dusk.local, container bindings and mocks, Laravel Pennant for feature-flag scenarios, and seeded fixtures for database state. The assessment recommends exhausting these before adding a Dusk-only micro-package. If Pennant or a per-test hook covers your scenarios, skip the dependency.
- Is alebatistella/duskapiconf actively maintained?
- The assessment reports a single release in August 2023, a single maintainer, four stars, and zero dependents, so downstream bug discovery is effectively absent. Treat it as a pattern to evaluate rather than a default dependency. If you adopt it, wrap it behind an internal helper so removing it is a one-file change.
- How do I reset configuration between Dusk API tests with alebatistella/duskapiconf?
- The provided context does not document a reset or teardown API, and the assessment explicitly flags mid-test failure and state reset as open questions. Design your base Dusk test case to restore configuration in tearDown regardless of the package's behavior. Verify with a deliberately failing test that state does not leak into later scenarios.
- Can I use alebatistella/duskapiconf with parallel Dusk tests?
- Parallel safety is not confirmed in the provided context and is listed as an open question in the assessment. If Dusk runs in parallel, shared file or cache state could cause cross-test interference until proven otherwise. Start with a serial spike or isolate state per process before scaling the suite.