- What Laravel versions does this package support, and how do I ensure compatibility?
- This package explicitly requires PHP 8.4+ and is designed for Laravel 10.x. To ensure compatibility, test it in a sandbox environment matching your Laravel version. Use Composer’s `platform-check` in your `composer.json` to enforce version constraints and avoid conflicts with other dependencies.
- Does this package work with Lumen or non-Laravel PHP applications?
- This package is Laravel-centric, relying on Symfony Console, Doctrine Migrations, and Laravel’s service container. While it *might* work in Lumen with manual adjustments (e.g., binding services via `app.bind()`), non-Laravel PHP apps would require significant refactoring to replicate Laravel’s kernel, migrations, and asset pipeline.
- How do I install and configure the package for production?
- Run `composer require baks-dev/wildberries-manufacture`, then install assets and migrations with `php bin/console baks:assets:install` followed by `php bin/console doctrine:migrations:migrate`. Review the generated database schema for conflicts with your existing tables, and ensure your `.env` includes the required Wildberries API credentials.
- What Wildberries APIs does this package interact with, and are they publicly documented?
- The package interacts with Wildberries’ internal order fulfillment and production APIs, but the README does not specify which endpoints or contracts are used. Engage with the maintainer for API documentation or mock the dependencies using tools like VCR recordings (e.g., `vcrphp`) to test locally without live API calls.
- Can I customize the production workflow (e.g., add pre/post-processing hooks)?
- The package provides a foundation for Wildberries order production but lacks explicit documentation on extensibility points. You may need to override service bindings in Laravel’s container or extend existing classes. Check for events or observer patterns in the codebase, or fork the package if deep customization is required.
- How does this package handle API failures, such as rate limits or schema changes?
- The package likely uses Guzzle or a similar HTTP client, but error handling specifics (e.g., retries, exponential backoff) are undocumented. Review the source code for `HttpClient` configurations or implement middleware in Laravel to manage retries and logging. Consider adding circuit breakers for resilience.
- Are there any known conflicts with existing Laravel configurations (e.g., service providers, middleware)?
- The package includes its own Doctrine migrations and Symfony Console commands, which *could* conflict with custom Laravel configurations. Isolate its resources by namespacing or overriding service bindings via `app->bind()` in a service provider. Test thoroughly in a staging environment before production deployment.
- Does this package support batch processing for high-volume Wildberries orders?
- The package does not explicitly document batch processing capabilities. If your use case requires handling large volumes, test performance under load and consider integrating Laravel Queues for async processing. Monitor memory usage and database transaction sizes to avoid bottlenecks.
- How can I test this package without hitting the live Wildberries API?
- Use VCR recordings (e.g., `vcrphp`) to mock API responses during testing. Alternatively, leverage Pest or Mockery to stub the HTTP client dependencies. Run the PHPUnit tests with the `--group=wildberries-manufacture` flag to validate core functionality in isolation.
- What maintenance or long-term risks should I consider before adopting this package?
- The package appears actively maintained (version 7.4.19 as of the latest check), but monitor for updates or forks if development stalls. Risks include undocumented API dependencies, potential Laravel version drift, and migration conflicts. Plan for rollback strategies and consider forking if critical changes are needed.