Weave Code
Syncopate Bundle Laravel Package
phillarmonic/syncopate-bundle
Syncopate Bundle is a PHP package packaged as a Symfony bundle, providing a convenient integration layer for applications using Composer. Add it to your project to enable its services and configuration with minimal setup.
Symfony bundle for integrating with SyncopateDB
Frequently asked questions about Syncopate Bundle
- Is phillarmonic/syncopate-bundle a Laravel package or a Symfony bundle?
- phillarmonic/syncopate-bundle is described as a Symfony bundle that wires Syncopate services into the Symfony dependency injection container. The -bundle naming and overview point to Symfony conventions rather than native Laravel idioms such as service providers, facades, or publishable config. Treat it as Symfony-first until its composer.json and source confirm Laravel compatibility.
- How do I install phillarmonic/syncopate-bundle with Composer?
- Run composer require phillarmonic/syncopate-bundle and register the bundle using Symfony's bundles.php or kernel configuration. In Laravel there is no equivalent bundle registration step, so you would need a custom service provider wrapper if the underlying library is framework-agnostic. Pin a reviewed version, such as v1.5.0, until the v1.6.0 change is understood.
- Does phillarmonic/syncopate-bundle support Laravel 10 or Laravel 11?
- The provided context does not confirm any Laravel version support; it identifies the package as a Symfony bundle. Check composer.json for laravel/framework or illuminate/support constraints and for Symfony component requirements. If those constraints are absent, do not assume Laravel 10 or Laravel 11 compatibility.
- What does the v1.6.0 'Truncate features' change actually do?
- The v1.6.0 changelog entry 'Truncate features' is ambiguous and could mean adding a truncation capability, trimming features, or truncating stored data. Only the first interpretation is safely additive under semantic versioning. Review PR #9 and the v1.5.0...v1.6.0 diff before enabling it.
- Is it safe to upgrade from v1.5.0 to v1.6.0 in production?
- Do not upgrade blindly; a minor release should be backward-compatible, but the changelog does not rule out destructive truncation behavior. Install v1.6.0 in a branch with a disposable database, run your existing suite, and add targeted tests around any delete or truncate code paths. Keep v1.5.0 pinned as the rollback target until the change is characterized.
- How do I configure Syncopate Bundle in a Symfony or Laravel application?
- The bundle exposes configuration through standard Symfony config files and its DI extension. Confirm the available config keys, defaults, and whether any truncation behavior is opt-in. Laravel users would need to replicate this via a custom config file and service provider.
- Can I use its Symfony services, events, and console commands in Laravel?
- The package registers services in Symfony's container and advertises framework-native events and console command support for Symfony. Laravel uses a different container, event dispatcher, and Artisan command registration, so these features are not drop-in replacements. You would need adapter bindings and should check for Symfony component conflicts in your dependency graph.
- How should I test Syncopate Bundle before deploying to production?
- Start with a local install and smoke test against a disposable database, then run your existing test suite. Add focused tests for service definitions, configuration defaults, and the truncation path including failure handling. Deploy to staging with any new truncation behavior disabled before promoting to production.
- Is phillarmonic/syncopate-bundle actively maintained and safe to depend on?
- Maintenance risk is elevated by single-maintainer concentration and terse release notes with no visible CI or coverage signal in the provided context. Watch the repository for follow-up patches and review the license and known vulnerabilities before depending on it. Be prepared to vendor or fork if releases become stale.
- What are Laravel-native alternatives to Syncopate Bundle?
- For Laravel, the safer alternative is to use the Syncopate library directly with a custom service provider, facade, and config publishing if the library is framework-agnostic. If Syncopate Bundle is Symfony-only, look for a Laravel-specific bridge or keep the integration isolated behind your own adapter. Evaluate a maintained fork only after confirming the license permits it.
Weaver
How can I help you explore Laravel packages today?