Weave Code
Core Application Bundle Laravel Package
imanaging-document/core-application-bundle
Core application bundle for the iManaging Document ecosystem, providing shared Laravel/PHP scaffolding, service wiring, and foundational document-management components. Use it to bootstrap compatible iManaging projects and integrate related packages; verify version requirements before installation.
imaning-document/core-application-bundle is the foundational PHP bundle for the iManaging document platform, providing the shared application layer that other document-management packages build upon. It centralizes core services, configuration, and domain contracts so that document handling logic stays consistent across the suite.
- Core application layer with shared service definitions and configuration
- Document domain contracts for consistent integration across bundles
- Dependency injection setup for wiring services into your application
- Extensible architecture designed to be composed with companion packages
- PHP-native implementation with no framework lock-in
Frequently asked questions about Core Application Bundle
- Is imanaging-document/core-application-bundle a Laravel package?
- No. Despite being triaged as a Laravel/PHP package, the -bundle suffix and repository structure identify it as a Symfony bundle built around extension classes, compiler passes, and service definitions loaded by a Symfony kernel. Laravel has no bundle bootstrap and uses service providers and facades instead, so the package is not idiomatic for Laravel.
- Can I install this bundle in a Laravel application?
- Technically yes, but not sensibly by default. Consuming a Symfony bundle in Laravel requires a Symfony kernel-like bootstrap: registering the bundle, resolving its extension, compiling the container, and dispatching Symfony events. Reconstructing that inside a service provider means writing a mini-kernel or adopting an unsupported bridge, which is high effort and fragile.
- How do I install imanaging-document/core-application-bundle?
- For a Symfony application, install with Composer, register the bundle in your kernel or bundles.php, and configure its extension. For Laravel there is no supported installation path and no package auto-discovery contract, so adding it to composer.json is not recommended. Read composer.json first to confirm PHP and symfony/* constraints.
- Which Laravel versions does this package support?
- There are no officially supported Laravel versions because this is a Symfony bundle. The last release was 2022-06-02 and it likely targets Symfony 4.4 or 5.x with PHP 7.4 or 8.0-era constraints. Laravel 10 and 11 require Symfony 6 or 7 components, so expect incompatibility rather than support.
- Will this package conflict with Laravel's Symfony components?
- Very likely. A stale bundle pinned to Symfony 4.4 or 5.x will fight Laravel 10 or 11, which require Symfony 6 or 7 components during Composer resolution. Check the exact symfony/* constraints in composer.json before attempting anything. The realistic outcome is a dependency conflict, not a clean install.
- What does the core application bundle actually provide?
- It provides shared foundation services, configuration, and integration points for building document-centric applications on the imanaging platform. The name suggests framework-internal glue for wiring DI, routing, and configuration rather than a reusable feature library with a clean public contract. Audit the extension class and service definitions to find any domain classes worth extracting.
- Is this package maintained and safe for production?
- Treat it as high risk. The last release was 2022-06-02, the project has 2 stars and zero dependents, and its health score is 0.01 with no downstream validation. Test coverage, CI status, security-patch posture, and maintainer responsiveness are unknown. The MIT license is permissive, but that does not offset abandonment risk.
- How do I integrate document management features from this bundle into Laravel?
- Do not install the bundle. Audit the repository, copy the specific classes that justify interest into a local namespace behind an anti-corruption adapter, and rewrite configuration and DI wiring as Laravel service providers and config files. Add contract tests around the adapted behavior. Consider fork-and-maintain only if the audit reveals substantial non-trivial logic.
- What should I check in the repository before using it?
- Start with composer.json for PHP and symfony/* constraints, then read the bundle extension class and service definitions to see what is actually wired. Check for a test suite, CI pipeline, static analysis baseline, and any maintainer response history. Ask what concrete capability this bundle provides that maintained Laravel packages or first-party code do not.
- Are there better alternatives for document management in Laravel?
- Yes. A maintained Laravel package or first-party implementation is a better fit than a stale Symfony bundle, because it will follow Laravel idioms, service providers, and supported framework versions. If your team is on Symfony the bundle is at least idiomatic, though still stale. Evaluate your document-management requirements and choose a dependency with active support.
Weaver
How can I help you explore Laravel packages today?