- Can I use mnavarrocarter/problem-details-bundle in a Laravel application?
- Not directly. It is a Symfony bundle built around kernel.exception listeners, container-tagged auto-registration, and serializers for Symfony HttpFoundation, Doctrine, and Security exceptions. Laravel has App\Exceptions\Handler and no bundle auto-discovery or tag-based subscriber registration, so installing the package does not give you Laravel integration. The practical path is reading its payload-shaping logic and reimplementing it in Laravel's handler or a custom renderer.
- How do I install mnavarrocarter/problem-details-bundle?
- It is installed via Composer, but the package assumes Symfony framework-bundle semantics and bundle registration. The provided context does not include the exact composer require command or configuration, so check the repository and composer.json constraints first. It does not ship a Laravel service provider or Laravel auto-discovery support.
- Does this package support Laravel 10 or Laravel 11?
- There is no documented Laravel support in 0.1.0. The package still orbits Symfony components, and although Laravel 10 and 11 ship Symfony 6 and 7 components, the bundle's listener and tag registration machinery is not present in Laravel. Dependency resolution must be re-verified, because a version bump is not evidence of Laravel compatibility.
- What does RFC 7807 Problem Details actually give my API?
- It gives your API a standard error payload with type, title, status, detail, and instance members, usually served as application/problem+json. Instead of ad-hoc error shapes, clients get consistent structured errors. In this package, exceptions are converted into those responses automatically within Symfony.
- How do I create custom problem types with this bundle?
- The package advertises custom problem types via simple classes and configurable type, title, status, detail, and extension fields. The exact class contract and serialization behavior are defined in the source, not in the release notes. For Laravel, you would reimplement equivalent problem classes or array payloads inside your exception handler.
- Is 0.1.0 stable enough for production?
- No. A 0.1.0 initial release is by definition an unstable, unproven API with no production track record. The technical assessment flags high API instability and notes no visible CI, release process, or triage evidence yet. Treat it as pre-production input, not a production dependency.
- Which exceptions does it map automatically?
- The 0.1.0 notes describe an exception listener plus serializers for Doctrine, HttpFoundation, and Symfony Security exceptions. Laravel's exception set does not translate one-to-one, so ValidationException, AuthenticationException, AuthorizationException, ModelNotFoundException, ThrottleRequestsException, and TokenMismatchException need re-derivation. The mapping table must be rebuilt against Laravel rather than copied.
- Does it support RFC 9457, the newer Problem Details standard?
- The release notes do not mention RFC 9457, so assume RFC 7807 2016 semantics until the source shows otherwise. The two standards are structurally near-identical, with differences mainly in wording and type URI guidance. Verify the serialization surface before relying on RFC 9457 behavior.
- Is mnavarrocarter/problem-details-bundle actively maintained?
- The maintenance picture is unresolved. Metadata previously indicated a 2018 release, while 0.1.0 is labelled Initial Release, which suggests a rewrite, a re-tag, or a different lineage. One release after dormancy is a restart, not a proven cadence, and no security response path or CVE process is stated.
- How should I test a Laravel port of this bundle's behavior?
- Use contract tests for the application/problem+json shape, status codes, content negotiation, extension fields, and each mapped Laravel exception. The technical assessment estimates roughly one to three engineer-days including contract tests. Test Laravel's own exception classes rather than assuming Symfony exception behavior carries over.