Weave Code
Core Bundle Laravel Package
softspring/core-bundle
Softspring Core Bundle provides a shared foundation for Softspring PHP applications, bundling common services, base classes, and utility helpers that keep projects consistent and reduce boilerplate across your stack.
This bundle provides common symfony features.
Frequently asked questions about Core Bundle
- Is softspring/core-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It has no service providers, facades, or Laravel-style configuration publishing, so you cannot install it into a Laravel application. Laravel developers looking for an equivalent shared foundation should use Laravel service providers or a dedicated Laravel base package instead.
- How do I install softspring/core-bundle with Composer?
- Run composer require softspring/core-bundle in your project root. The overview states installation is done via Composer and Symfony Flex, so Flex should register the bundle automatically. If you do not use Flex, add the bundle class manually to config/bundles.php.
- Which Symfony and PHP versions does softspring/core-bundle support?
- Supported versions are declared in the bundle's composer.json require constraints rather than in the overview, so check the repository or Packagist before installing. Composer will refuse an install that conflicts with your current framework version. Because the bundle is a shared foundation, keep your other Softspring packages on matching releases to avoid constraint conflicts.
- Do I need Symfony Flex to use this bundle?
- Flex is the recommended path and the overview lists simple installation via Composer and Symfony Flex. Without Flex you can still install the package and register the bundle entry in config/bundles.php yourself. Any bundle-provided configuration can then be created manually under config/packages.
- What services and configuration does the bundle register by default?
- It ships ready-to-use service definitions, dependency injection defaults, and shared parameter conventions that Softspring projects rely on. The bundle is intentionally a base layer, so most of its value is in consistent defaults rather than user-facing features. Review the bundle's config and services files before overriding anything, since other Softspring packages may depend on those definitions.
- Can I use softspring/core-bundle outside the Softspring ecosystem?
- Technically yes, because it is a plain Symfony bundle with standard service definitions. However, its main benefit is lightweight integration with the wider Softspring ecosystem, so standalone projects get less value. If you only need a few helpers, copying those utilities may be simpler than adding a dependency.
- How do I test an application that uses this bundle?
- Register the bundle in the kernel used by your test environment, exactly as you do in development. Functional tests can then boot the kernel and pull the shared services from the container, while unit tests can instantiate helper classes directly. Keep the bundle at a fixed minor version in CI so shared service signatures do not shift unexpectedly.
- Does softspring/core-bundle add runtime overhead in production?
- The bundle is described as lightweight and mostly contributes container definitions, configuration, and utility helpers. That means the main cost is compile-time container work, which is cached once you warm up the cache. Run bin/console cache:warmup during deployment and the shared definitions become plain cached PHP.
- How do I override or disable the bundle's default services?
- Use standard Symfony dependency injection: redefine a service ID in your app's services.yaml or adjust the relevant parameters under config/packages. Compiler passes are the right tool when you need to modify definitions programmatically after the bundle loads. Be careful when removing shared services, as other Softspring packages may expect them to exist.
- What are the alternatives to softspring/core-bundle?
- For Symfony, the common alternatives are symfony/framework-bundle plus your own small internal bundle, or a Composer path repository that holds shared code across projects. For Laravel, the equivalent patterns are package discovery, service providers, and shared config files. Choose the bundle when you are already on the Softspring stack and want its conventions for free.
Weaver
How can I help you explore Laravel packages today?