- Does baks-dev/wildberries-package work with Laravel?
- The README documents Symfony/BaksDev-style commands such as php bin/console and Doctrine migrations, not Laravel Artisan or Eloquent. No Laravel service provider or Laravel version support is mentioned. Laravel teams should inspect composer.json, package registration, and console commands before assuming compatibility.
- How do I install baks-dev/wildberries-package?
- Install with composer require baks-dev/wildberries-package, then run php bin/console baks:assets:install to publish configuration and assets. Apply database changes with doctrine:migrations:diff and doctrine:migrations:migrate. These are Symfony console commands, so Laravel users need an equivalent or bridge, and PHP 8.4+ must be available.
- What does this Wildberries package actually do?
- It is a PHP 8.4+ module for Wildberries order packaging, adding Doctrine entities, configuration, assets, and database schema for packaging-task accounting. The README excerpt does not document catalog sync, inventory, labels, or Wildberries API client behavior. Treat it as a domain module rather than a complete Wildberries integration.
- Does baks-dev/wildberries-package call the Wildberries API?
- The README focuses on packaging orders, installation, Doctrine migrations, and testing; it does not document API authentication, order import, status transitions, labels, rate limits, or retries. You must inspect the source to confirm whether any Wildberries API calls exist. If you need full API integration, plan additional development.
- What are the requirements for baks-dev/wildberries-package?
- It requires PHP 8.4+ and Composer, and the documentation assumes Doctrine migrations plus BaksDev/Symfony console conventions. Confirm your CI, hosting, and production runtime support PHP 8.4 before installing. Laravel users should also verify Doctrine compatibility and command registration.
- How do I test baks-dev/wildberries-package?
- The README shows php bin/phpunit --group=wildberries-package, indicating a dedicated PHPUnit test group. No pass rate or PHP 8.4 CI results are published in the excerpt. Run the group in an isolated environment and add your own integration tests around migrations and packaging workflows.
- Is baks-dev/wildberries-package production-ready?
- It is MIT-licensed and versioned, but the assessment notes 0 stars, 0 dependents, and version-only changelog entries, which signals low adoption. For production, pin an exact version, vendor or fork if strategic, inspect generated migrations and SQL, and test rollback. Require internal ownership and monitor releases for breaking changes.
- What database tables and migrations does baks-dev/wildberries-package create?
- The package uses Doctrine migrations; you generate schema changes with doctrine:migrations:diff and apply them with doctrine:migrations:migrate. The README does not list table names, foreign keys, or indexes. Run the diff in a disposable database and inspect SQL, constraints, and rollback before touching production data.
- Does it support multi-account, multi-warehouse, or partial shipments?
- The README excerpt does not document multi-account, multi-warehouse, or partial shipment behavior. These capabilities depend on the package entities and any API integration, which you must verify in source and schema. Do not assume support without inspecting the models and testing those scenarios.
- What alternatives exist for Wildberries integration in Laravel?
- This package is narrow and Symfony/Doctrine-oriented, so Laravel teams may evaluate native Wildberries API SDKs, custom API clients, or Laravel-specific fulfillment modules. The assessment recommends treating it as a domain accelerator rather than a platform foundation. Compare scope, API coverage, maintenance, and framework fit before choosing.