- Is smartbox/core-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. The -bundle suffix, the Symfony bundle layout with a Bundle class plus a DependencyInjection extension and config tree, and the Smartbox Group provenance all point to Symfony kernel integration, and v1.8.0 registers a JMS Serializer visitor through Symfony's DI compiler-pass machinery. It is not a Laravel package, so do not expect a service provider, a facade, or a config/core-bundle.php file.
- Does smartbox/core-bundle work with Laravel?
- Not realistically. Nothing in the bundle maps onto Laravel's service container, package discovery, or serialization stack, and its JMS Serializer visitor hooks into an API that has no Laravel equivalent. You could in theory extract the plain PHP utilities, but at that point you are forking rather than installing.
- How do I install smartbox/core-bundle with Composer?
- Run composer require smartbox/core-bundle and register the bundle in your Symfony kernel's bundles array. Composer has to resolve the Symfony and JMS Serializer constraints at the same time, so run composer require --dry-run first to see whether the dependency graph is satisfiable in your project. There is no Laravel package discovery, so nothing auto-registers.
- Which PHP and Symfony versions does smartbox/core-bundle support?
- The last known constraint profile suggests PHP 7.2 to 7.4 and Symfony 4.4 to 5.x, but the v1.8.0 release note names no version and nothing indicates PHP 8.4 or Symfony 7 readiness. Confirm by reading the php, symfony/*, and jms/serializer constraints in composer.json rather than assuming. A dry-run install is the fastest way to see what your project will actually resolve to.
- Why does smartbox/core-bundle depend on JMS Serializer?
- JMS Serializer is a first-class integration, not an incidental transitive dependency. v1.8.0 adds a custom serializer visitor, which means the bundle customises the serialization and deserialization pipeline rather than merely providing domain services. Visitors hook into graph navigation and are tightly coupled to the serializer's internal API, so this dependency is the most version-sensitive part of the stack.
- Is smartbox/core-bundle actively maintained?
- There is a pulse: v1.8.0 landed after a long gap following a 2020-05-11 predecessor. But the release is one narrow feature with a one-sentence note, no migration path, no linked pull request, and no test evidence, which is not the same thing as a support relationship. Treat it as single-maintainer with an unreviewable cadence.
- What are the alternatives to smartbox/core-bundle for Laravel?
- For serialization in Laravel you would use Eloquent API Resources, spatie/laravel-data, or Symfony Serializer rather than JMS Serializer, so the bundle's main value proposition does not translate. If you need shared services and utilities across Laravel projects, a small in-house package built on Laravel's own container and config is usually less risk than adopting an unmaintained Symfony bundle.
- How should I evaluate smartbox/core-bundle before using it in production?
- Start with a composer require --dry-run to answer the go/no-go cheaply, then read composer.json for the php, symfony/*, and jms/serializer constraints. Check the release history, the test suite, and whether bundled assets have been audited, since the MIT licence does not imply review. Because the bundle touches a deserialization visitor, audit input coercion plus null and empty-string handling before it meets real data.
- What are the risks of the JMS Serializer visitor added in v1.8.0?
- A visitor is the part of a serializer integration most likely to break across JMS Serializer majors, which changed namespaces, attribute handling, and graph and visitor APIs between 1.x, 2.x, and 3.x. If you fork the bundle, you inherit responsibility for a visitor written against an API you did not choose. Behaviourally, plain-text deserialization means loosely typed input is coerced into domain objects, which is exactly where silent type-juggling bugs live.
- Can I fork smartbox/core-bundle and use it in Laravel?
- You can, since it is MIT licensed, but the fork drops the Bundle class, the DI extension, and the JMS Serializer visitor and keeps only the plain PHP utilities. That leaves you absorbing maintenance for a package with zero stars, zero dependents, and no public bug corpus to lean on when something breaks. For most Laravel teams, reimplementing the handful of utilities you actually need is cheaper.