- Is baks-dev/yandex-market a Laravel package or a Symfony bundle?
- Despite being described as Laravel in some write-ups, every artifact points to Symfony: bin/console for asset install, Symfony Messenger transports, and retry strategies expressed as Messenger options. Plan on this being a Symfony-first bundle consumed by a Laravel application, not a Laravel-native package. That correction typically adds roughly a sprint to the integration estimate.
- How do I install baks-dev/yandex-market and publish its config and assets?
- Run composer require baks-dev/yandex-market, then execute php bin/console baks:assets:install to install the configuration and file resources. Note the bin/console entry point rather than artisan, which confirms the Symfony console foundation. The package requires PHP 8.4 or newer.
- What PHP and Laravel versions does baks-dev/yandex-market require?
- The package has a hard PHP 8.4+ floor, which effectively forces Laravel 11+ or a deliberate PHP upgrade of your application. Treat this as an infrastructure prerequisite rather than a package detail, because it can drag PHP runtime and CI changes across your whole estate.
- How does baks-dev/yandex-market isolate queue workers per seller token?
- Each token gets its own Messenger transport, configured with a queue_name per profile plus a retryStrategy using maxRetries(3), delay(1000), and multiplier(2). This means one noisy token generating 429s or 401s cannot stall another seller's catalog sync. In Laravel you would map this to a queue-per-token topology with Horizon supervisors.
- Does baks-dev/yandex-market support webhooks for order status or price updates?
- No, the package has no webhook support. Order-status and price-indexing events must be received via Yandex's native webhooks into a controller you own. Budget for that second integration surface, since the package does not reduce it.
- How do I run the tests for baks-dev/yandex-market?
- Execute php bin/phpunit --group=yandex-market to run the package's test group. Because there is no visible endpoint coverage matrix, also write contract tests against the Yandex sandbox and enumerate which endpoint families the package actually wraps.
- Are API calls in baks-dev/yandex-market idempotent and safe to retry?
- Retry idempotency semantics are not documented, so retry safety sits with the caller. Enforce idempotency keys at your own adapter layer, cap retries at 3 with exponential backoff, and route exhausted jobs to a dead-letter queue.
- Does baks-dev/yandex-market own database tables for tokens or seller profiles?
- Persistence ownership is unspecified, and Symfony bundles frequently ship Doctrine entities and migrations, which Laravel cannot use directly. The safer posture is to own token storage in your encrypted config store and treat the package as a stateless consumer. Confirm schema ownership in a spike before committing to a roadmap.
- How should I integrate baks-dev/yandex-market into a Laravel application safely?
- Use ports and adapters: define MarketplaceClient, CatalogSync, and OrderFeed interfaces in your domain and implement them by delegating to this package. For queues, either run Symfony Messenger consumers under Supervisor alongside Horizon, or translate the work into Laravel jobs, which is cleaner operationally and recommended beyond a pilot. Fork the package into your org namespace on day one given the maintenance risk.
- What are the main risks of adopting baks-dev/yandex-market?
- It has a single maintainer and zero stars, and its release notes simply repeat the version string. A possible transitive baks-dev core dependency could mean adopting a framework rather than an API client, so resolve that in a one-week dependency spike with a hard go/no-go gate. Also verify provenance, signing, and Packagist ownership before adoption.