- What is micro-module/null used for in Laravel or PHP applications?
- It provides a lightweight no-op implementation of a micro-module contract, so code that expects a module can run without side effects. It is intended for testing, feature-flagging, bootstrapping, and as a safe fallback when a real module is not bound. It is framework-agnostic and dependency-free, so it is not a replacement for Laravel's native queue or module features.
- Is micro-module/null a Laravel queue driver?
- No. It targets a PSR-style queue or micro-module abstraction, not Laravel's Illuminate\Contracts\Queue\Queue contract or queue connectors. Laravel will not auto-wire it as a queue driver without an adapter, and using it as one would intentionally drop messages. Treat it as a dev-only test double or null object, not a production queue backend.
- How do I install micro-module/null for Laravel tests?
- Install it as a development dependency with composer require --dev micro-module/null. Verify its PHP version constraint and interface dependency against your project before adding it to CI. Keep it out of production installs by using composer install --no-dev and environment guards, and document that it is test-only.
- Does micro-module/null work with Laravel Queue::fake() and Bus::fake()?
- They solve different problems. Queue::fake() and Bus::fake() are the native Laravel tools for faking dispatch and making assertions against Laravel's queue and bus contracts. micro-module/null is only useful when your code intentionally depends on a PSR-style module or queue abstraction and needs a zero-behavior implementation.
- Can I use micro-module/null in production?
- You should not. The package is described as zero behavior, so accidental production binding would silently discard jobs or module calls and can break asynchronous workflows. Restrict it to tests or explicitly guarded bootstrapping paths, and make production binding fail loudly instead of falling through to a no-op.
- Which queue interface and version does micro-module/null implement?
- The package description says it implements the Micro Module contract with a PSR-style abstraction, but the exact interface and version still need verification in composer.json and the package source. PHP does not have a broadly ratified PSR for queues, so confirm what your application and tests actually type-hint. Do not assume compatibility with Laravel's native queue contract.
- How do I bind micro-module/null in a Laravel test container?
- Bind the relevant module or queue contract to the package's null implementation in a test-only service provider or test case setup. The package is framework-agnostic and should not require a Laravel service provider, but Laravel will not auto-wire it without an adapter or explicit binding. Verify the exact class name and interface from the installed package before wiring it.
- Does micro-module/null record dispatched jobs for test assertions?
- No, it is a no-op implementation with no state, I/O, or configuration, so it should not be relied on to record dispatched jobs. For Laravel dispatch assertions, use Queue::fake() or Bus::fake(). If you need a PSR-style fake that records calls, build or use a small in-memory test double instead.
- What are alternatives to micro-module/null for testing queues in Laravel?
- For standard Laravel code, Queue::fake() and Bus::fake() are the first choice. You can also use Mockery or a project-owned null object or in-memory fake behind your own test helper. Use micro-module/null only when your code already depends on the matching PSR-style abstraction and you need a zero-dependency placeholder.
- Is micro-module/null maintained and safe to depend on?
- The repository is read-only, has zero stars and dependents, and shows no community validation, so strategic risk is high even though runtime risk is low in tests. Budget for version pinning, security review, and a fork or replacement path. Timebox a pilot and prefer a small internal fake if the package does not remove meaningful test complexity.