- Is netbull/core-bundle compatible with Laravel?
- No, not as a Laravel package. The netbull/core-bundle name, Symfony-style namespace, and bundle lifecycle point to a Symfony bundle, and Laravel has no kernel-bundle registration or Symfony DependencyInjection extension model. Only framework-agnostic PSR code, traits, or value objects could be reused, and only if they are not coupled to Symfony components.
- How do I install netbull/core-bundle in a Laravel app?
- You generally should not install it in a Laravel app expecting normal Laravel integration. In Symfony it would be installed with Composer and registered as a bundle, but that wiring is not used by Laravel. If you only need isolated utilities, fork or vendor the PSR-only parts under the MIT license after auditing them.
- Which Laravel and Symfony versions are supported?
- The provided context does not list PHP, Symfony, or Laravel version constraints, and there is no Laravel support indicated. The v7.0.x release line suggests an active Symfony-oriented release process, but not Laravel compatibility. The v7.0.11 modernization patch may have moved dependency constraints, so read composer.json and the commit diff rather than assuming support.
- Can I reuse NetBull CoreBundle traits and base entities in Laravel?
- Possibly, but only after auditing each class for Symfony contracts and hidden dependencies. Core bundles often contain opinionated base classes, so inheriting them can tightly couple your domain layer to vendor abstractions. Because the package is MIT licensed, a fork-and-vendor approach is viable if the reusable surface is small and clean.
- Is netbull/core-bundle safe to use in production?
- For a Laravel codebase, treat it as high risk because the framework wiring is unusable and only partial reuse is plausible. For a Symfony codebase, risk is lower but still needs review: the project has zero stars, zero dependents, and no visible downstream production validation. Pin by commit SHA, review every diff, and avoid inheriting deeply from its base classes unless you accept the coupling.
- What changed in v7.0.11 and is it a breaking change?
- The release is a single commit labeled modernization with no body, no linked issue, and no BREAKING CHANGE marker. At patch level that is suspicious because modernization often means dependency constraint bumps, removed PHP or Symfony versions, or internal API refactors. Read the diff before upgrading and do not trust the patch number as proof of safety.
- Why are NetBull CoreBundle release dates in 2026?
- Two consecutive tags are dated 2026-06-11, which points to a timestamp or clock offset in the publishing pipeline or a mirrored repository rather than a reliable activity signal. The date field cannot tell you whether the project is fresh or abandoned. Inspect the commit log and release diffs instead.
- Does NetBull CoreBundle work with Doctrine?
- That is not established by the provided context. Core bundles commonly ship base entities, traits, and helpers that may depend on Doctrine or specific Symfony versions, and transitive constraints are unknown. Check composer.json, then run an integration test against your pinned Doctrine and Symfony versions before relying on it.
- How should I test netbull/core-bundle before adopting it?
- Start by inspecting composer.json, PSR-4 autoloading, and imports for Symfony DependencyInjection, HttpKernel, or Doctrine coupling. Build an isolated Symfony test app or PHPUnit harness around only the classes you intend to use, then run static analysis and your own compatibility tests. Pin the dependency by SHA and diff every version bump.
- What alternatives to netbull/core-bundle should I consider?
- Laravel teams should prefer Laravel-native packages with service providers and clear framework support. Teams needing shared primitives can use framework-agnostic PSR packages or extract only the specific traits and helpers they need. Symfony teams should favor maintained bundles with visible dependents, issue history, and a compatibility matrix.