Weave Code
Common Laravel Package
numberninecms/common
Common foundation package for NumberNine CMS, offering shared PHP and Laravel utilities, base classes, helpers, and support code used across the CMS ecosystem. It helps keep modules consistent and reduces duplication when building or extending NumberNine applications.
Number Nine Common provides the shared foundation for the Number Nine CMS ecosystem — reusable helpers, contracts, and base classes that keep Laravel-powered modules consistent and lightweight.
It bundles the utilities every Number Nine package depends on, so you can build custom blocks, modules, and extensions without duplicating glue code.
- Shared service providers and configuration defaults
- Common contracts and abstract base classes
- Helpers for assets, paths, and settings
- Consistent DTOs and reusable traits
Frequently asked questions about Common
- What is numberninecms/common used for?
- It is the shared foundation package for the NumberNine CMS ecosystem, providing common utilities, helpers, contracts, and reusable components that the other NumberNine modules build on. Its purpose is to keep CMS code consistent across modules so individual packages do not duplicate the same low-level logic. In practice you usually get it as a transitive dependency when you install a NumberNine package rather than requiring it directly.
- How do I install numberninecms/common with Composer?
- Install it like any other Composer package with composer require numberninecms/common. Because it is shared infrastructure, it is normally pulled in automatically alongside the core NumberNine packages, so check whether it already appears in your composer.lock before adding it manually. After installing, inspect the package's composer.json for any PHP or Laravel version constraints that must match your application.
- Which Laravel versions does numberninecms/common support?
- The package is described as Laravel based, but the provided overview and README excerpt do not list explicit framework version constraints. Check the illuminate/support requirement in the package's composer.json on Packagist to confirm compatibility with your application's Laravel version. If you are upgrading Laravel, verify that constraint before running composer update.
- Do I need numberninecms/common if I am not using NumberNine CMS?
- It is intended primarily as internal shared infrastructure for NumberNine modules, so its public API is not documented as a general-purpose utility library. You could technically call its helpers from any Laravel app, but there is no stated backwards-compatibility guarantee for standalone use. For unrelated projects, prefer Laravel's built-in Str, Arr, and Collection helpers or a dedicated utility package.
- What does numberninecms/common actually contain?
- According to the package description it ships common utilities, helpers, contracts, and reusable components shared across the NumberNine ecosystem. The contracts are interfaces that other NumberNine modules implement or depend on, which is what keeps the modules loosely coupled. Browse the package source directories and namespaces after installation to see exactly which helpers and contracts are available in your version.
- How do I configure numberninecms/common in a Laravel app?
- The README excerpt provided does not document any configuration file, service provider bindings, or publishable assets. After installing, check whether the package registers a service provider and whether any config file can be published with php artisan vendor:publish. If there is no config file, the package is likely intended to work without manual setup.
- Is numberninecms/common safe to use in production?
- It is a normal Composer dependency that other NumberNine modules rely on, so treat it with the same care as any production package. Pin the version in your composer.lock, review release notes before upgrading, and run your test suite after each update. Since it contains shared helpers and contracts, a breaking change here can ripple through every NumberNine module in your project.
- How do I test code that depends on numberninecms/common?
- Because the package targets Laravel, you can exercise it inside your application's existing test suite or in isolation with a package testing harness such as Orchestra Testbench. Unit test any helpers you call directly so an upgrade in the shared package cannot silently change behaviour. Contracts are useful here because you can bind test doubles to the interfaces in your own code.
- What are the alternatives to numberninecms/common?
- If you are committed to the NumberNine CMS ecosystem, there is no real substitute because the other modules depend on these shared contracts. If you only need the helper utilities, Laravel's own illuminate/support components cover most string, array, and collection needs. For generic package scaffolding, tools like spatie/laravel-package-tools or Orchestra Testbench are common choices.
- How is numberninecms/common maintained and versioned?
- The package metadata supplied here does not list a public repository URL, so check Packagist for the release history, version tags, and the linked source location. Follow semantic versioning conventions when constraining the version in composer.json, and review changelogs before minor or major upgrades. Because it is shared infrastructure, treat it as a foundational dependency and keep it aligned with the versions your other NumberNine modules require.
Weaver
How can I help you explore Laravel packages today?