- How do I install paloma/shop-client in a Laravel application?
- Install it as a normal Composer dependency with composer require paloma/shop-client. The package is a thin SDK rather than a Laravel framework component, so installation is straightforward but you should expect to wire configuration and container bindings yourself. Verify the package's PHP, Laravel, and Guzzle constraints against your application's pinned versions before committing.
- Does paloma/shop-client support Laravel 10, 11, and 12?
- The provided evaluation does not confirm a supported Laravel version matrix, so do not assume Laravel 10, 11, or 12 compatibility without checking. Inspect the package composer.json for PHP, Laravel, and Guzzle constraints and run a short spike in your actual application version. If the package has no service provider, Laravel integration depends mainly on your own binding and configuration code.
- Does paloma/shop-client include a service provider or facade for Laravel?
- There is no visible indication that the package ships a Laravel service provider, facade, or config publish step. Plan to register a configured client instance in your own service provider and bind it as a singleton behind an application-owned interface. That approach keeps config caching and dependency injection predictable in production.
- How do I configure authentication for the Paloma Shop API?
- Authentication, endpoint configuration, and credentials handling are integration work you should expect to own. Store Paloma credentials through your existing secrets path such as environment variables or Vault rather than committing them to config files. Then bind a configured client instance in Laravel and wrap it behind an interface so the rest of the codebase never imports Paloma namespaces directly.
- What shop operations does paloma/shop-client support?
- The package is described as wrapping common storefront requests for products, carts, and orders through a fluent interface. The evaluation warns that support may be a subset, so confirm whether it covers the operations you actually need, such as idempotent order submission, pagination, and webhook signature verification. Run a timeboxed spike against a sandbox tenant and prove one representative read and one write end to end.
- How should I handle errors and retries with paloma/shop-client?
- The error surface is a stated technical risk: determine whether the client exposes typed exceptions or lets raw Guzzle exceptions bleed through. Review timeout, retry, and idempotency-key behavior before relying on it for order writes. Wrap calls behind your own gateway interface so you can add retries, logging, and translation to domain errors without leaking vendor details.
- Is paloma/shop-client safe to use in production with zero stars?
- Treat it as a single-vendor, effectively unvetted dependency because the repository shows zero stars and zero dependents. A June 2025 release is a positive activity signal, but a low quality score suggests thin tests or documentation. Pin the client to an exact or tilde constraint, contain it behind an adapter, and keep a feature flag so you can revert if the vendor contract or package changes.
- How do I test Laravel code that uses paloma/shop-client?
- Do not let Paloma client classes spread through your application. Bind the client behind an application-owned interface such as ShopGateway, then fake or mock that interface in unit and feature tests. For integration confidence, use a sandbox tenant and assert one real read and one real write complete successfully before cutover.
- What are alternatives to paloma/shop-client for a Laravel integration?
- The package only makes sense if Paloma Middleware is already your system of record or is being evaluated as one. If Paloma is not in your architecture, a custom HTTP client or direct Guzzle integration may be a smaller commitment than adopting a zero-adoption SDK. If you do adopt it, keep the adapter boundary so you can replace it with another client later.
- How is paloma/shop-client maintained and versioned?
- The evaluation does not confirm an SLA, changelog, named maintainer, or documented Shop API version contract, so ask the vendor directly. The client is a facade over Paloma's HTTP contract, meaning you inherit their breaking changes more than this repository's. Pin the dependency, audit Composer conflicts in CI, and clarify whether the package is intended for external consumption or primarily for Paloma's own integrations.