Weave Code
Core Laravel Package
esensi/core
Core foundation package for the Esensi Laravel ecosystem, providing shared service providers, configuration, helpers, and base utilities. It gives modular Laravel applications a consistent starting point for integrating Esensi components.
The foundational components of Esensi
Frequently asked questions about Core
- What is esensi/core used for in a Laravel application?
- esensi/core is the foundational package of the Esensi ecosystem. It ships shared service providers, configuration files, helper functions, and base utilities that the other Esensi components build on. If you are not using any other Esensi packages, it provides little value on its own because its job is to give modular applications a consistent starting point. Treat it as infrastructure glue rather than a feature package.
- How do I install esensi/core with Composer?
- Add it to your project with composer require esensi/core and let Composer resolve a version compatible with your framework constraints. On a Laravel 12 application the current line is v4.1.0; on Laravel 10 or 11 you may be pinned to an older release. After installing, clear your config cache so the package's merged configuration is picked up. No manual provider registration should be needed if the package relies on Laravel's package discovery.
- Does esensi/core support Laravel 12?
- Yes. Version 4.1.0 is described in its changelog as an upgrade to Laravel 12, which indicates the maintainers are actively tracking the framework release train. That said, the changelog is a single line and does not document whether older Laravel versions remain supported. Read the require block in the package's composer.json at the v4.1.0 tag to confirm the exact illuminate/* constraint before committing to an upgrade.
- What PHP version does esensi/core v4.1.0 require?
- Laravel 12 requires PHP 8.2 or newer, so a package that targets Laravel 12 almost certainly raises its own php constraint to 8.2 as well. The changelog does not state this explicitly, so verify the php entry in the package's composer.json rather than assuming. If any of your applications still run PHP 8.1, expect a hard install-time failure when you attempt the bump. That failure is loud and easy to diagnose, but it can disrupt an in-flight sprint.
- Is upgrading to esensi/core v4.1.0 a breaking change for Laravel 10 or 11 apps?
- It depends entirely on how the illuminate constraints were changed. If they widened to something like ^11.0|^12.0, the release is additive and safe across your fleet. If they narrowed to ^12.0 only, then a minor version bump silently drops support for older frameworks, and Laravel 10 and 11 applications will be pinned to v4.0.x and stop receiving fixes. Compare the require block at v4.0.x and v4.1.0 before upgrading.
- How do I configure esensi/core in my Laravel project?
- Most Esensi configuration is expected to flow through published config files and environment variables, following standard Laravel package conventions. Publish any package config with the vendor:publish command, then review the resulting file rather than editing files inside the vendor directory. Because the repository's documentation is thin, read the package's service providers and config files directly to see which keys are actually consumed.
- Do I need esensi/core if I only use one Esensi component?
- esensi/core is the shared foundation that other Esensi packages depend on, so it is usually pulled in transitively when you install a component. If you are only using a single package, check whether that package requires esensi/core before adding it directly to your composer.json. Adding it alone provides helpers and base utilities but no end-user features, so it rarely justifies inclusion on its own.
- How should I test an application that depends on esensi/core?
- Run your normal Laravel test suite after bumping the package, and pay attention to any tests that touch configuration resolution or container bindings, since those are the areas shared service providers affect. In CI, test against the exact framework versions you support rather than only your production version. Given the sparse release notes, adding a smoke test that boots the application and resolves the Esensi providers is a cheap way to catch regressions early.
- Is esensi/core actively maintained?
- The v4.1.0 release upgrading the framework constraint to Laravel 12 is a positive maintenance signal, because it means the package has not been left behind on the release train. However, the changelog for that release is a single line with no linked pull request, migration note, or deprecation notice. That pattern suggests thin release documentation, so verify behavior from the diff and the composer.json rather than relying on release notes.
- What are good alternatives to esensi/core?
- For most applications, the shared functionality Esensi provides is already available through Laravel's own service container, configuration repository, and helper functions. Projects that adopted esensi/core primarily for modular structure often substitute packages like nwidart/laravel-modules or a hand-rolled package discovery setup. If you are evaluating esensi/core anew, confirm that your team is actually adopting the wider Esensi ecosystem before adding a foundation layer you would otherwise not need.
Weaver
How can I help you explore Laravel packages today?