- Is nti/sync-bundle a Laravel package or a Symfony bundle?
- nti/sync-bundle is a Symfony bundle, not a Laravel package. It ships as NTISyncBundle with Symfony bundle registration, DI container extension classes, and a Symfony configuration tree. Laravel's service provider model does not consume those natively, so treat it as a Symfony artifact when evaluating fit.
- Can I use nti/sync-bundle in a Laravel application?
- Only conditionally. Direct integration is poor because there is no Eloquent integration, Laravel queue or event hooks, configuration publishing, or service provider. Viable paths are to decouple the sync engine from the bundle wrapper and reuse it as a plain Composer library, deploy it as a standalone Symfony sync service that Laravel calls over HTTP or a queue, or fork the code and own it.
- How do I install nti/sync-bundle with Composer?
- Run composer require nti/sync-bundle. Composer installation is straightforward because the package is MIT licensed and resolvable in principle. In Laravel you will still need to register or wire the engine yourself, since there is no Laravel service provider to auto-discover.
- Which Laravel versions does nti/sync-bundle support?
- None officially. The package is a Symfony bundle with no Laravel service provider, no Eloquent integration, and no Laravel-native configuration. Compatibility with Laravel 10 or 11 is unverified and should be treated as a custom integration project, not a supported path.
- What PHP, Symfony, and Doctrine versions does nti/sync-bundle require?
- The last release was July 2023, so it likely targets PHP 8.0 or 8.1 and Symfony 5 or 6. Bundle code commonly assumes Doctrine ORM or DBAL and Symfony components, each of which adds coupling cost. Always check the composer.json constraints and resolve them against your current stack before designing around it.
- What does nti/sync-bundle actually synchronize?
- It synchronizes data between applications and Doctrine-backed storage. The bundle provides configurable sync definitions, field mapping, conflict handling, and extensible handlers for importing, updating, and reconciling records. It does not advertise Eloquent support, so Laravel models would need a separate adapter layer.
- Is nti/sync-bundle actively maintained?
- No. The last release was July 2023 with no subsequent activity, and the package has roughly three stars and zero dependents. Assume no upstream fixes and no community support. That profile favors adopting the source code rather than depending on it as a library.
- Does nti/sync-bundle handle conflict resolution, idempotency, and partial failures?
- The bundle advertises conflict handling and extensible handlers, but the README does not document idempotency or partial-failure recovery in detail. Sync engines fail subtly in ordering, retries, and resume paths, so verify behavior in code and tests before trusting it. If the behavior is implicit, budget time to make it explicit.
- What license is nti/sync-bundle released under, and can I fork it?
- It is MIT licensed, which permits forking, vendoring, and internal modification. Given the stale maintenance and zero dependents, a fork-and-own strategy is often more realistic than depending on the upstream package. Keep the license notice and treat the fork as source code your team maintains.
- How should I test nti/sync-bundle before using it in production?
- Start by inspecting composer.json constraints and the ratio of bundle scaffolding to domain logic, because the value may live in the engine rather than the Symfony wrapper. Look for integration tests that exercise failure, retry, and resume paths, and add your own contract tests around conflict resolution and idempotency. If coverage is missing, treat correctness as unknown and either fork with tests or build a Laravel-native alternative using queues, events, and Eloquent.