- How do I install baks-dev/wildberries-products in a Laravel app?
- Run composer require baks-dev/wildberries-products, then publish configuration and assets with php bin/console baks:assets:install. After that, generate and apply Doctrine migrations using doctrine:migrations:diff and doctrine:migrations:migrate. In a Laravel deployment, run these steps in your build or release pipeline.
- What Laravel and PHP versions does baks-dev/wildberries-products require?
- The package is listed for PHP 8.4+ and the technical evaluation notes Laravel 10+ as the expected framework baseline. If your application runs Laravel 8 or 9, you would need to upgrade or build a compatibility bridge. Always confirm the constraint against the package's composer.json before installing.
- Does this package use Doctrine migrations or Eloquent models?
- Yes. The documented setup relies on Doctrine migrations to update the database schema, and the evaluation notes Doctrine/Eloquent integration. Run doctrine:migrations:diff first so you can review the generated SQL for conflicts. Then apply changes with doctrine:migrations:migrate in a controlled environment.
- Can I use baks-dev/wildberries-products without running console commands?
- The documented install uses console commands such as baks:assets:install and Doctrine migration commands. Serverless or locked-down container environments may not allow CLI execution at runtime, so run these commands during deployment. The evaluation flags console-dependent workflows as an integration risk.
- How does this package handle Wildberries API authentication and rate limits?
- The provided overview does not document the exact Wildberries authentication flow, so verify whether your integration needs API keys or OAuth2. The evaluation recommends confirming token refresh behavior and credential storage before production use. For rate limits, implement exponential backoff and queue-based throttling.
- Is baks-dev/wildberries-products suitable for syncing product variants like sizes and colors?
- The module is product-centric, but the provided materials do not detail how Wildberries variants such as sizes, colors, articles, and offers are mapped. The evaluation explicitly lists variant handling as a key question to validate. Inspect the schema and models before assuming it fits your catalog structure.
- What are the risks of schema conflicts when integrating this Wildberries module?
- Schema conflict risk is rated high because the module adds Doctrine migrations to an existing database. Watch for table or column clashes such as products versus wildberries_products and for missing SKU uniqueness constraints. Run doctrine:migrations:diff, review the SQL, and use prefixes or custom migrations where needed.
- How should I test baks-dev/wildberries-products in my Laravel project?
- The README shows a baseline command: php bin/phpunit --group=wildberries-orders. The evaluation notes low testing coverage, so add integration tests for your own sync, inventory, and error-handling workflows. Also test asset publishing and migrations in a staging database.
- Does the package support events, webhooks, or queues for real-time product updates?
- The evaluation says the package lacks explicit event hooks, but you can layer Laravel observers or custom events such as ProductSynced on top. Webhook support is not confirmed in the provided materials, so do not assume real-time updates. Use queues and transactions to manage consistency and rate limits.
- What alternatives or maintenance considerations exist for Wildberries product integration in Laravel?
- If you need a non-product domain, API-first architecture, or stronger event-driven behavior, compare this module with a custom Wildberries API integration or a more abstract marketplace package. The MIT license allows forking and modification if the module is close but not exact. Monitor Wildberries API changes because maintenance risk is rated medium.