Weave Code
Pincore Laravel Package
pinoox/pincore
Pinoox Pincore is the lightweight core of the Pinoox PHP framework, offering routing, MVC structure, dependency injection, modular packaging, and essential utilities for building fast, maintainable web applications with minimal configuration. Composer-ready and designed for simple, scalable PHP deve...
At a glance
Frequently asked questions about Pincore
- Is pinoox/pincore a Laravel package or a standalone PHP framework core?
- Pinoox Pincore is the lightweight core of the Pinoox PHP framework, not a conventional Laravel package. It provides routing, MVC structure, dependency injection, modular packaging, and essential utilities. Laravel teams can evaluate it for modular architecture, but it should be treated as Laravel-adjacent or standalone integration work rather than a drop-in Laravel package.
- How do I install pinoox/pincore with Composer?
- Install it with Composer using the package name pinoox/pincore, and pin a version such as v3.14.12 for evaluation. Confirm the PHP and Composer requirements from the package metadata before integrating it into a Laravel application. Keep explicit Composer PSR-4 mappings as a fallback while validating bootstrap and autoload behavior.
- Does pinoox/pincore support Laravel 10 or Laravel 11?
- The provided context does not publish a Laravel version support matrix, so compatibility with Laravel 10, Laravel 11, or other versions must be verified directly. Test against your target Laravel and PHP versions, including Composer 2 optimized autoloading and package discovery. Treat Laravel support as an integration validation task, not an assumed guarantee.
- How does pincore dynamic sub-app discovery work with Composer autoloading?
- Version v3.14.12 dynamically discovers sub-apps and registers their PSR-4 namespaces at runtime, reducing manual Composer wiring for modular domains. This runtime classloader behavior must be reconciled with Composer 2 optimized autoloading and Laravel's Composer-first autoloading model. Prove that discovery is deterministic, cached where needed, and compatible with your deployment artifacts.
- Is pincore sub-app discovery run on every request or cached?
- The provided evaluation flags this as a key question and does not confirm whether discovery runs per request or is bootstrapped once. For production, require environment gating, allowlisting, or caching so discovery does not add filesystem scan overhead on every request. Validate the behavior under your web server, OPcache configuration, and deployment pipeline.
- How do I prevent namespace collisions or duplicate class resolution in pincore?
- Inventory existing sub-apps, namespaces, and Composer PSR-4 mappings before enabling broad discovery. Start with a narrow allowlist in development and compare discovered candidates against the known app inventory. Test for duplicate app names, missing apps, and accidental loading of development-only sub-apps before production.
- Is pincore safe for production Laravel deployments?
- It can be feasible for modular monolith or platform-style deployments, but the evaluation rates technical risk medium to high until proven in your target Laravel application. Production safety depends on controlling discovery, avoiding namespace collisions, handling OPcache and preloading, and keeping deployments deterministic. Use a pinned evaluation branch and prove parity before removing explicit Composer autoload entries.
- Does pincore work with OPcache preloading and immutable deployments?
- The context says compatibility with OPcache preloading and immutable deployment pipelines must be validated. Dynamic PSR-4 registration can leave stale OPcache or weaken deployment determinism if it is not explicitly controlled. Test preloading, containerized filesystems, symlinked releases, and CI path resolution before relying on it.
- How should I test pinoox/pincore in a Laravel application?
- Create a pinned v3.14.12 evaluation branch, inventory sub-apps and namespaces, and run discovery in development only first. Test cross-app autoloading with a narrow allowlist, then compare discovered classes against Composer's autoload map. Include Windows, macOS, and Linux path cases, symlinks, Composer 2 optimized autoloading, and OPcache scenarios.
- What are alternatives to pincore for modular Laravel development?
- Laravel-native options include Composer path repositories, package discovery, service providers, and modular monolith patterns using explicit PSR-4 mappings. Pincore is strongest where you need plugin or sub-app isolation and shared domain access, but it is less suitable for small Laravel apps or teams requiring strict Laravel package conventions. Evaluate it as an optional modular runtime capability rather than a default autoloading strategy.
Weaver
How can I help you explore Laravel packages today?