- What is nicolasguilloux/wiremock-bundle used for?
- It is a Symfony bundle that integrates WireMock so you can stub and simulate HTTP services in your PHP test suite. The goal is faster, more reliable integration tests that do not depend on real external APIs. It is Symfony-oriented rather than a Laravel-native package, so Laravel teams should confirm how they would wire it into the framework.
- How do I install nicolasguilloux/wiremock-bundle?
- Run composer require nicolasguilloux/wiremock-bundle, typically with --dev because this is test tooling. The captured 1.0.0 release has no documented install steps, PHP floor, or dependency constraints, so inspect composer.json before adding it to a locked project. Expect to provide a WireMock server that your test suite can reach.
- Does nicolasguilloux/wiremock-bundle work with Laravel?
- It is described as a Symfony bundle, and there is no evidence in the captured metadata of a Laravel ServiceProvider, facade, or illuminate support constraints. Laravel auto-discovery therefore should not be assumed, and a compatibility spike is needed before adoption. For many Laravel-only HTTP mocking needs, the framework's built-in Http::fake is a simpler option.
- Which Laravel and PHP versions are supported by wiremock-bundle?
- The captured metadata does not include composer.json constraints, a PHP version floor, or any statement about Laravel 10, 11, or 12 support. The 1.0.0 tag alone does not prove compatibility with any framework version. Check the repository's composer.json and test matrix before treating it as compatible with your runtime.
- Do I need Java or Docker to run WireMock with this bundle?
- WireMock itself normally runs as a separate Java process, commonly from a standalone JAR or a Docker image. The bundle's role is to help configure and talk to that server from your Symfony test setup. Plan for a WireMock service in local development and CI rather than expecting an in-process PHP mock.
- Can I use wiremock-bundle to mock third-party APIs in CI?
- Yes, that is the intended pattern: stub the external HTTP service with WireMock and let your tests call the stubs instead of real APIs. You will need a WireMock instance available in the CI job, for example as a service container. This can make integration tests faster and less flaky, but the undocumented setup must be proven in your pipeline.
- How does wiremock-bundle compare to Laravel Http::fake or other mocking tools?
- Laravel's Http::fake and Http::preventStrayRequests are built in, require no extra service, and cover most Laravel HTTP client tests. Alternatives include php-http/mock-client, Symfony's MockHttpClient, or running WireMock standalone without this bundle. Choose this bundle only if WireMock-style stub management and a real HTTP boundary are important to your test strategy.
- Is nicolasguilloux/wiremock-bundle production-ready and actively maintained?
- The captured assessment shows only a first 1.0.0 release, no changelog detail, and no documentation beyond the package description. It appears to be a single-author first release, so there is no evidence yet of release cadence, responsiveness, or CVE handling. Treat maintenance and API stability as unproven until you inspect the repository history and issue activity.
- What license does nicolasguilloux/wiremock-bundle use?
- The license is not stated in the metadata provided for this evaluation. Check the repository's LICENSE file and the license field in composer.json before distributing or relying on the package commercially. Do not assume MIT or any other permissive license until it is confirmed.
- How should a Laravel team evaluate wiremock-bundle before adopting it?
- Run a short, time-boxed spike in a throwaway branch: inspect composer.json, README, tests, and license, then install it as a dev dependency in a sandbox clone. Confirm whether anything auto-registers, whether global config or routing is affected, and whether a WireMock server can run in your CI. Finish with a smoke test and an explicit adopt, defer, or reject decision based on dependency weight and maintenance signals.