- What is idmarinas/common-bundle used for?
- It collects shared utilities, base classes, traits, helper functions, default configuration, and conventions used across idmarinas projects. It is intended to reduce boilerplate in Symfony applications by providing consistent building blocks for strings, arrays, dates, services, controllers, and entities. It is a lightweight foundation rather than a complete framework feature set.
- Is idmarinas/common-bundle a Laravel package?
- No. The package is explicitly a Symfony bundle designed to be registered in a Symfony bundles.php file, and it does not provide Laravel service providers, config publishing, or facade conventions. Laravel teams should treat it as Symfony-oriented source code rather than a drop-in Laravel dependency. For a Laravel codebase, its architectural fit is poor out of the box.
- Does idmarinas/common-bundle work with Laravel?
- Not natively. Using it in Laravel would mean pulling in Symfony kernel or bundle machinery, or cherry-picking individual source files and helpers. There is no Laravel integration layer, so most Laravel applications should prefer a Laravel-first package or copy only the small helpers they need.
- Which Laravel versions does idmarinas/common-bundle support?
- There is no declared Laravel version support because this is not a Laravel package. Its Composer constraints target Symfony and PHP versions, which you should inspect directly in composer.json. Do not assume compatibility with any Laravel release without verifying the Symfony and PHP constraints against your application.
- How do I install idmarinas/common-bundle with Composer?
- Install it with Composer using composer require idmarinas/common-bundle. In Symfony, register the bundle in config/bundles.php according to its documentation. In Laravel, installation alone will not wire it up, so you would need custom integration or selective copying of helpers, and production use should pin an exact version.
- How do I configure idmarinas/common-bundle in a Symfony application?
- Register the bundle in bundles.php, then override its sensible default configuration per project as needed. Review the bundle's service definitions and enable or audit only the services your application actually uses. Consult the published documentation for current configuration keys and registration details.
- Is idmarinas/common-bundle safe for production use?
- The BSD-3-Clause license is permissive and commercially safe. However, the project has a single maintainer, very few stars, zero dependents, and no public production-usage evidence, so you would likely be the first real integrator. Audit the helpers you rely on, pin the version, and monitor releases. Also check whether the bundle registers global services or event subscribers that could add hidden runtime cost.
- What changed in idmarinas/common-bundle version 3.6.0?
- Version 3.6.0 is a minor bump from 3.5.1, which by semantic versioning suggests backward-compatible additions rather than breaking changes. The release notes are opaque and mainly link to documentation and a changelog compare URL, without summarizing features, deprecations, or fixes. Read the compare diff before adopting it, especially to see whether any new services load on boot.
- What are alternatives to idmarinas/common-bundle for Laravel projects?
- Laravel already provides many equivalents through Str, Arr, Carbon, and framework helpers, so an internal Support or Helpers namespace can replace much of this package in around 50 lines. For Symfony, rely on Symfony components and well-maintained bundles with clearer support matrices. Choose alternatives that match your host framework and have active maintenance and dependent usage.
- How should I test idmarinas/common-bundle integration in my application?
- Start with unit tests around each helper or base class you depend on, because external battle-testing evidence is limited. In Symfony, boot the kernel in the test environment and verify that registered services load without errors. Add smoke tests for routes and console commands, and pin the package version in CI so upgrades require an explicit review.