- What is kami/api-core-bundle used for?
- kami/api-core-bundle is a reusable API core package for PHP applications that bundles common building blocks for JSON APIs, including request and response handling, standardized error payloads, pagination, filtering, and validation hooks. It is intended to help teams standardize endpoints and reduce boilerplate so they can focus on domain logic. The description says it integrates cleanly with Laravel and Symfony-style applications, so confirm your framework target before adopting it.
- Is kami/api-core-bundle a Laravel package or a Symfony bundle?
- The name uses Symfony bundle terminology, but the package description positions it as a framework-friendly core that integrates cleanly with Laravel and Symfony-style applications. Before adopting it for a Laravel estate, inspect composer.json and the package structure to confirm whether it is Laravel-native or Symfony-first with Laravel shims. The description alone does not settle that question, and it is the highest-value check to make first.
- How do I install kami/api-core-bundle in a Laravel app?
- The intended integration path is to install the package with Composer, publish any provided configuration, and wire in the base controllers, middleware, response helpers, and validation hooks. Mechanically the wiring is usually small; the real effort is validating behavior and accepting the response and error contract. Treat installation as an experiment with a revert plan, and verify the require block against your PHP and Laravel versions before scheduling a change.
- Which Laravel and PHP versions does kami/api-core-bundle support?
- The provided context does not include a version matrix or specific Composer constraints, so support for Laravel 10, Laravel 11, PHP 8.2, or PHP 8.3 is not established here. Read composer.json for the actual PHP and framework requirements, and look for a CI matrix proving those versions rather than relying on a constraint line alone. If the package is pinned to one framework major, treat adoption as a one-way decision.
- What features are included in kami/api-core-bundle?
- It includes unified JSON response envelopes for success and error states, pagination and filtering helpers for list endpoints, a validation layer with structured error output, request and response handling, base controllers, middleware, and route scaffolding. Components are described as extensible and overridable through configuration, but you should confirm the exact scope before adoption because scope equals blast radius.
- How does kami/api-core-bundle handle errors and validation?
- The package provides standardized error payloads and a pluggable validation layer with structured error output, and the technical evaluation also notes exception-to-JSON rendering and middleware. Those code paths are security-sensitive because middleware and exception renderers sit on every request and can leak stack traces, internal IDs, SQL fragments, or auth context if misconfigured. Review debug-mode behavior in non-production environments explicitly before trusting the package in production.
- Can I customize the response envelope or override components in kami/api-core-bundle?
- The package is described as extensible, with components that can be overridden or swapped through configuration. In practice that means publishing config and subclassing or replacing the provided controllers, middleware, and helpers where needed. Keep in mind that the envelope and error schema become a de facto public API, so customization is a contract decision that affects every client and generated SDK.
- Is kami/api-core-bundle safe for production use?
- The technical evaluation flags adoption and abandonment risk as the dominant concern, citing low adoption signals, a single-maintainer profile, and no release cadence evidence. Middleware and exception renderers sit on every request, so a formatting bug can expose stack traces, internal identifiers, or auth context. Use it only with a named owner willing to fork and pin it, a clear test and static-analysis baseline, and a documented replacement path.
- What are alternatives to kami/api-core-bundle for Laravel APIs?
- Alternatives include building your own baseline with Laravel's built-in response, validation, and pagination features, or adopting a more established API package. The value of kami/api-core-bundle is convention rather than novel capability, so it saves time only when its opinion about envelopes, errors, and validation matches yours. For mature services with an established envelope and error taxonomy, retrofitting usually means breaking client contracts or maintaining two shapes.
- How should I test kami/api-core-bundle before adopting it?
- Start with a spike in a throwaway Laravel API service: install it with Composer, publish config, wire in the middleware and base controllers, and exercise success responses, validation failures, exceptions, and paginated list endpoints. Check the exception renderer with debug mode on and off, and verify Composer constraints against your PHP and Laravel majors. Then measure the boilerplate it removes across two or three real services in engineer-hours to size the business case.