Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Laravel Common

Laravel Common Laravel Package

jeroennoten/laravel-common

A shared utility package for Laravel by Jeroen Noten, collecting common helpers, traits, and service-provider plumbing used across his packages. It reduces duplication and offers a small, lightweight foundation for building or extending related Laravel projects.

View on GitHub
Deep Wiki
Context7

Laravel Common Things

Frequently asked questions about Laravel Common
What is jeroennoten/laravel-common used for?
It is a shared utility package by Jeroen Noten that collects common helpers, traits, and service-provider plumbing used across his Laravel packages. Its stated purpose is to reduce duplication and provide a small, lightweight foundation for building or extending related Laravel projects. If you work in that package ecosystem, it can supply reusable building blocks instead of copy-pasted code.
How do I install jeroennoten/laravel-common with Composer?
Install it with composer require jeroennoten/laravel-common. Before running that in a real application, check the package's composer.json for its PHP and illuminate/* constraints, because the only compatibility signal provided here is a v1.1.0 changelog entry adding Laravel 5.3 support. Composer will refuse the install if your framework version does not satisfy the declared range.
Does jeroennoten/laravel-common support Laravel 10, 11, or 12?
The supplied context does not establish support for Laravel 10, 11, or 12. The only published compatibility evidence is a v1.1.0 changelog line adding support for Laravel 5.3, which is a long end-of-life release. Inspect the package's composer.json illuminate/* constraint and its CI matrix before assuming modern Laravel compatibility.
Do I need to register a service provider or publish config for this package?
Check the package's composer.json for extra.laravel.providers and aliases entries; if they are present, Laravel auto-discovery registers the provider for you. If not, add the service provider manually in config/app.php. There is no evidence in the provided overview of publishable configuration or migrations, so verify with vendor:publish --list before relying on either.
What helpers and traits does jeroennoten/laravel-common actually include?
The package is described as collecting common helpers, traits, and service-provider plumbing shared across Jeroen Noten's packages. The exact class and function list is not included in the supplied overview, so browse the src directory on GitHub or run composer show to enumerate it. Treat any undocumented helper as internal until you have verified its behavior against your Laravel version.
Is jeroennoten/laravel-common safe to use in production?
Use caution, because the available evidence is a single old changelog line about Laravel 5.3 support with no data on last commit, open issues, PHP floor, or test matrix. For production, check Packagist release dates, GitHub commit cadence, and whether the package's tests run against your Laravel and PHP versions. Until that is confirmed, treat it as legacy-oriented rather than actively maintained for current framework majors.
Can I use jeroennoten/laravel-common directly in an application, or is it only for other packages?
It is a utility library designed to be shared across packages, so it can be required directly by an application as well as by another package. The overview does not state that it must be paired with any specific Jeroen Noten package. Review its composer.json requires to see whether it pulls in illuminate/* components or other dependencies you would rather not add.
How do I test whether this package works with my Laravel version?
Run composer update with your application's Laravel constraint and confirm the resolver accepts the package, then exercise your test suite. A successful install only proves constraint resolution, not runtime behavior, so cover the helpers and traits you actually call. Ideally also check the package's own CI matrix for the Laravel and PHP majors you deploy.
What does the v1.1.0 'Support L5.3' changelog entry mean?
It means the maintainers shipped a minor release that adds compatibility with Laravel 5.3, which is long past end-of-life. The entry alone does not tell you whether support came from widening illuminate/* constraints or from actual code changes for 5.3 features. It also does not indicate the newest Laravel version the package supports, so read the diff rather than relying on the changelog line.
Are there alternatives to jeroennoten/laravel-common?
For most applications, Laravel's built-in helpers such as Str, Arr, and Collection, plus standard service-provider conventions, cover the same ground without an extra dependency. Consider this package when you specifically want the shared plumbing used by Jeroen Noten's packages or are extending that ecosystem. If you only need one or two helpers, implementing them locally avoids coupling to an uncertain maintenance cadence.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
robertmarney/lara-hierarchial-collections
simonschaufi/rule-doc-generator
emissaoja/emissaoja
blackbricksoftware/gravityforms-civicrm-form-processor
al-rahabi/fancy-crud
jinas/dhivatar-component
mltstephane/laravel-quality
bernskiold/laravel-talentlms
bernskioldmedia/laravel-form-architect