Weave Code
Core Laravel Package
honey-comb/core
Core package for HoneyComb, providing foundational Laravel/PHP service providers, configuration, and shared utilities for building modular applications and packages.
Honey Comb Core is the foundational package for the Honey Comb ecosystem, providing a lightweight module system for Laravel applications. It lets you organize large codebases into self-contained, discoverable modules—each with its own routes, views, migrations, and service providers—while keeping bootstrapping predictable and explicit.
Built on Laravel's service container, the core handles module registration, auto-discovery, and lifecycle hooks so modules can be dropped in without touching the application skeleton.
- Pluggable module discovery and registration
- Per-module service providers, routes, and migrations
- Laravel-native configuration and container bindings
- PSR-4 autoloading with zero-config defaults
- Extensible hooks for custom module lifecycles
Frequently asked questions about Core
- What is honey-comb/core and do I need to install it?
- honey-comb/core is the foundation package for the Honey Comb ecosystem. It provides shared contracts, service provider wiring, configuration, and general utilities used by the other Honey Comb components and by applications built on top of them. You normally install it as a base dependency, either directly or transitively when you require a Honey Comb component. If you only use standalone packages unrelated to Honey Comb, you do not need it.
- How do I install honey-comb/core with Composer?
- Install it with Composer using composer require honey-comb/core. Because it is designed for Laravel applications, Laravel's package auto-discovery should register the service provider without manual edits to config/app.php. If auto-discovery is disabled in your project, add the provider to the providers array yourself. After installation, check the README for any publishable configuration or migration steps.
- Which Laravel and PHP versions does honey-comb/core support?
- Version support is defined in the package's composer.json under the require section, so check that file for the exact PHP and illuminate/support constraints of the release you are installing. Always match the package's major version to your Laravel version before running Composer update. If you are on an older Laravel release, look for a tagged package version that lists a compatible framework constraint.
- Do I need to publish the configuration file for honey-comb/core?
- Publishing is only necessary if you need to override the package defaults. Most Laravel packages in this style expose a vendor:publish tag for their config file, so run the publish command documented in the README when you want a local copy in your config directory. Otherwise the package merges its own defaults at boot and works without any published files. Keep published config minimal so future package updates do not conflict with your overrides.
- What contracts and utilities does honey-comb/core actually provide?
- The package is described as offering shared contracts, service provider wiring, configuration, and utilities for Laravel and PHP projects. In practice that means interfaces other Honey Comb components type-hint against, plus bootstrapping code and helper classes that keep those components consistent. Review the source's contracts directory to see the exact interfaces available in your installed version, since the set can change between major releases.
- Does honey-comb/core support Laravel package auto-discovery?
- Yes, Laravel packages of this type typically declare their provider in the extra.laravel.providers section of composer.json, which enables auto-discovery. That means you generally do not need to register anything manually after composer require. If the provider is not loading, run composer dump-autoload and confirm the package is not listed in your application's dont-discover configuration.
- Can I use honey-comb/core in a plain PHP project without Laravel?
- It is built around Laravel service provider wiring, so it expects an application container to boot correctly. Some utilities and contracts may be usable standalone, but the intended integration path is a Laravel or Laravel-compatible application. If you need framework-agnostic behavior, check the individual classes for hard dependencies on illuminate/support before relying on them.
- How do I test a package or app that depends on honey-comb/core?
- Install it as a dev dependency alongside an orchestrator such as orchestra/testbench, which boots a minimal Laravel application for package tests. That lets your tests resolve the container bindings and contracts the core package registers. If you are writing unit tests only, you can mock the contracts directly instead of booting the framework. Pin the core package version in CI so test results stay reproducible.
- Is honey-comb/core production ready and how should I manage updates?
- Treat it like any foundational Composer dependency: pin it to a stable tagged release, commit your composer.lock, and review the changelog before bumping major versions. Because other Honey Comb components depend on it, a major bump can ripple through your dependency tree, so update and test in a staging environment first. Avoid tracking a development branch in production, since shared contracts can change without a semver signal.
- What are the alternatives to honey-comb/core, or how do I extend it?
- There is no direct drop-in replacement, because the package exists specifically to support the Honey Comb ecosystem rather than to solve a general framework problem. If you only need a specific utility, consider using Laravel's built-in support helpers or a focused package instead of the full core. To extend it, bind your own implementations against the published contracts in a service provider so the rest of the ecosystem keeps working unchanged.
Weaver
How can I help you explore Laravel packages today?