nvl / laravel-suite
Composer composition of all NVL Laravel Suite packages
Package info
github.com/nvl-laravel-suite/laravel-suite
Type:metapackage
pkg:composer/nvl/laravel-suite
Requires
- php: ^8.4
- nvl/activity: ^7.0
- nvl/auth: ^7.0
- nvl/auth-identity-bridge: ^7.0
- nvl/comments: ^7.0
- nvl/content: ^7.0
- nvl/core: ^7.0
- nvl/csv: ^7.0
- nvl/filterable: ^7.0
- nvl/forms: ^7.0
- nvl/mail-notification-bridge: ^7.0
- nvl/mail-notifications: ^7.0
- nvl/media: ^7.0
- nvl/metafields: ^7.0
- nvl/ownership: ^7.0
- nvl/pages: ^7.0
- nvl/primitives: ^7.0
- nvl/seo: ^7.0
- nvl/settings: ^7.0
- nvl/tasks: ^7.0
- nvl/taxonomy: ^7.0
- nvl/templates: ^7.0
- nvl/translatable: ^7.0
- nvl/translations: ^7.0
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
None
Replaces
None
README
The suite is a Composer metapackage selecting independent NVL packages. It has no application provider or domain services of its own. NVL Light targets PHP 8.4 and Laravel 13 and prepares a coordinated breaking family 7 release. Published 6.x releases use earlier contracts.
Prefer individual packages when the application needs a smaller dependency graph. Use the metapackage manifest for the exact selection. Billing and Payments are separate optional integrations. Native Ownership is configured explicitly; the retired Tenancy bridge is not a Light integration.
This Composer metapackage installs no files and therefore has no provider, config, migrations or skill folder of its own. Every installed runtime package supplies its own portable Agent Skill at resources/boost/skills, discovered by php artisan boost:install --skills. Publish configuration and migrations through the specific package tags documented in that skill; do not invent suite wrapper assets.
Applications own Actions, DTOs, controllers, routes, response resources and frontend types. Packages expose native services, Eloquent models, enums, domain values and documented arrays. Read the installed package's README and source PHPDoc for its policies, signatures and optional adapters.
Start with installation, getting started, consumer APIs, and UPGRADING.md. Package repositories in the NVL organization are public release mirrors; their versioned release history remains historical evidence.
Choose one migration source, configure required host bindings and run relevant Doctor commands before enabling features. Installation does not establish authorization or operational readiness. Preserve source connections, durable operation IDs, queue envelopes and recovery journals during deployment; rebuild caches and restart workers.
Released under the MIT License.