- Can I install jjanvier/crowdin-bundle in a Laravel application with Composer?
- No. It is a Symfony2 bundle and constrains symfony/framework-bundle to the 2.x line, which will not resolve against Laravel 9, 10, or 11 with their Symfony 6 or 7 components. Forcing installation with --ignore-platform-reqs creates a dependency graph you cannot patch or maintain. Use official Crowdin tooling or a thin Laravel wrapper instead.
- Does this package support Laravel 9, 10, or 11?
- No. Laravel does not use Symfony bundles; it uses service providers, facades, and Artisan commands. This bundle registers through Bundle::boot(), DependencyInjection extensions, and YAML service definitions that Laravel's container will not autoload or honor. There is no maintained bridge that lets a Symfony2 bundle run natively inside Laravel.
- How do I configure Crowdin credentials for this bundle in Laravel?
- You cannot configure it natively in Laravel. Configuration relies on Symfony2 DI parameters and YAML service definitions, while Laravel expects config files and environment variables. Porting the wiring into a Laravel service provider means rewriting the integration rather than adjusting a few settings, and the hidden Symfony DI coupling makes copy-paste porting non-trivial.
- What Crowdin API version does this bundle use, and is it still supported?
- The bundle and its php-crowdin-lib dependency target Crowdin API v1, which has been sunset. Calls will fail with auth or 404 errors regardless of code health, and php-crowdin-lib does not change endpoint generation. You need the v2 API through the official client or Crowdin CLI.
- Is jjanvier/crowdin-bundle maintained and safe for production?
- No. The bundle is a decade stale, and the 0.2.0 release merely delegates HTTP and Crowdin logic to php-crowdin-lib, another abandoned package. It pulls in old Guzzle and Symfony HTTP and console components with known or unpatchable CVE exposure. Community signal is effectively zero with 8 stars, 0 dependents, and no issue triage or forks doing maintenance work.
- What is the difference between this bundle and crowdin/crowdin-api-client-php?
- This project is a Symfony2 bundle wrapping old Crowdin API v1 operations, while crowdin/crowdin-api-client-php is the official, maintained v2 client that is compatible with PHP 8. The official client is portable and easier to wrap in Laravel Artisan commands. This bundle adds Symfony framework coupling without modern API support.
- Can I reuse the console commands from this bundle as Laravel Artisan commands?
- Not directly. They are Symfony console commands wired through Symfony2 dependency injection, so you would need to port the small, readable command logic into Artisan commands. The TPM assessment treats this as a pattern source rather than a library. You would still need to replace the Crowdin client with the v2 API.
- What are better alternatives for syncing Crowdin translations in Laravel?
- Use the official Crowdin CLI as a CI step, crowdin/crowdin-api-client-php for v2 API access, or a thin in-house wrapper over that client exposed as Laravel Artisan commands. These options fit Laravel's service provider and queue system and avoid Symfony2 dependency conflicts. The Symfony bundle does not fit a Laravel stack.
- How do I test a Laravel integration with this Crowdin bundle?
- You cannot meaningfully test it in Laravel because Composer will not resolve the Symfony2 dependency graph. Even with ignored platform requirements, the API v1 endpoints are sunset, so integration tests would fail at authentication or 404 responses. Test a v2 client or a CLI-based sync workflow instead.
- Should I fork this bundle to add Laravel support?
- Not recommended. Forking means owning Symfony2 DI and YAML rewiring, replacing php-crowdin-lib, and migrating to the v2 API, which is effectively a rewrite. You would still carry old dependency and security risk. A thin Laravel wrapper over the official v2 client is less work and more maintainable.