- Is parabol/parabol-base-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. The name ends in Bundle and the package is structured around Symfony's bundle model with a DI extension and compiled configuration. Laravel consumes Symfony components but does not load bundles, so expect a framework mismatch rather than drop-in support.
- Can I use parabol-base-bundle in a Laravel application?
- Not directly, and only with real porting work. Nothing in the package description claims Laravel support, there is no advertised service provider or illuminate/support dependency, and no public example of Laravel usage exists. The realistic path is to read the source, extract the plain-PHP utility or domain classes you actually need, and re-home them in your own package under your namespace.
- How do I install parabol/parabol-base-bundle with Composer?
- composer require parabol/parabol-base-bundle works like any Packagist package if it is published there, and in Symfony you then enable it in bundles.php. In Laravel the install alone accomplishes nothing because there is no service provider to register. Run composer show parabol/parabol-base-bundle afterwards to inspect constraints and dependencies before touching application code.
- Which PHP and Symfony versions does parabol-base-bundle support?
- The supported matrix is whatever composer.json declares, so check the require block for symfony/framework-bundle, symfony/http-kernel and the php constraint. There is no published compatibility table and no visible CI matrix in the package overview. Pin an explicit constraint in your composer.json instead of relying on a floating version.
- Does parabol-base-bundle register a Laravel service provider or publish config?
- There is no indication of a Laravel service provider, an extra.laravel entry, or publishable config, migrations and routes. For a Symfony bundle the equivalent wiring lives in a DependencyInjection extension and Resources/config files, which Laravel ignores entirely. Audit composer.json and src/ before assuming anything is auto-registered or auto-published.
- Is parabol/parabol-base-bundle actively maintained?
- There is no visible signal of activity: zero stars, zero dependents, no fork history and no production references in the overview. If you adopt it directly, you effectively become the maintainer of your own copy. Check the last commit date, release count and issue tracker before committing any product code to it.
- How should I evaluate parabol-base-bundle before adding it to a project?
- Start with composer.json rather than source review: look at framework constraints, the presence or absence of illuminate/support, autoload rules and transitive dependencies. Then scan src/ to see whether the classes are portable plain PHP or tightly wired to Symfony's container and kernel. That split tells you within an hour whether this is a one-day extraction or a multi-week port.
- What is a better alternative for shared base functionality in Laravel?
- Build a small internal package instead of depending on a base bundle. Laravel's package discovery and service providers make it cheap to ship shared config, helpers and base classes under your own namespace with your own tests. Extracting the few useful classes from parabol-base-bundle and pinning a note to the upstream commit is the lowest-risk route.
- Is parabol-base-bundle safe to use in production?
- The main risks are the framework mismatch, a bus factor of one, and no upstream patching path for transitive dependency CVEs. Base bundles are also invasive because application code inherits from their classes, which is cheap to adopt and expensive to unwind. If you must use it, wrap it behind your own interfaces so it stays replaceable.
- Can I fork parabol-base-bundle and maintain it internally?
- Forking is the recommended path if you need the code, but confirm the license in the repository first because it governs redistribution and attribution. Once forked, keep it under your own namespace, add tests and CI, and track upstream commits as a diff source rather than a live dependency. Never let product code extend its base classes directly, so the fork stays removable.