Weave Code
Core Laravel Package
sledgehammer/core
The foundational core package for Sledgehammer, providing shared utilities, base classes, and common functionality for Laravel and PHP applications. It serves as a consistent starting point for building and extending Sledgehammer-based projects.
sledgehammer/core is the foundational package for the Sledgehammer ecosystem, providing shared Laravel integrations, contracts, and utilities that keep companion packages consistent and lightweight. It offers a clean starting point for building modular applications without imposing heavy conventions.
- Laravel service provider and package discovery support
- Publishable configuration with sensible defaults
- Shared contracts and reusable helpers
- Extensible extension points for companion packages
- Composer-friendly core with minimal dependencies
Frequently asked questions about Core
- What is sledgehammer/core?
- Sledgehammer Core is the core package of the Sledgehammer framework, providing shared code and integration points used across the Sledgehammer ecosystem. It exists to give the individual Sledgehammer components a common foundation so features behave consistently from package to package. You typically do not build against it directly so much as rely on it being present underneath the components you install.
- How do I install sledgehammer/core with Composer?
- Install it with composer require sledgehammer/core from your project root. In most cases it will also arrive automatically as a transitive dependency of other Sledgehammer packages, so check composer show sledgehammer/core before adding it manually. Commit your composer.json and composer.lock after installing so the resolved version is reproducible across environments.
- Do I need to install sledgehammer/core directly, or does it come with other Sledgehammer packages?
- Because it is described as the common foundation for Sledgehammer components, it is usually pulled in automatically when you require one of those components. Installing it directly only makes sense if you are extending the framework or relying on its shared code yourself. Running composer why sledgehammer/core will show which package required it.
- Which Laravel and PHP versions does sledgehammer/core support?
- Version support is defined by the require constraints in the package composer.json, so check that file or the Packagist release page for the exact PHP and illuminate/support ranges. The package metadata available here does not list specific supported versions, so verify before upgrading Laravel. Pin to a tagged release and run your test suite after any framework major upgrade.
- Does sledgehammer/core register a service provider or use Laravel package auto-discovery?
- As an integration layer for Laravel, the package is expected to expose its bindings through a service provider, and Laravel's package auto-discovery normally registers it via the extra.laravel block in composer.json. Confirm this by inspecting the installed composer.json, and check the package documentation before registering anything manually in config/app.php. If you disable auto-discovery, you will need to add the provider yourself.
- Is there a config file I need to publish for sledgehammer/core?
- If the package ships publishable assets, you can expose them with php artisan vendor:publish and selecting the Sledgehammer provider or its tag. The provided package overview does not list specific config keys or publish tags, so review the package source or its documentation first. Publishing is optional in most Laravel packages and only needed when you want to override defaults.
- How can I verify that sledgehammer/core is installed and working correctly?
- Start with composer show sledgehammer/core to confirm the resolved version, then run php artisan about to see which providers Laravel has booted. You can also list registered bindings or run a small feature test that exercises the Sledgehammer component depending on the core. If the provider is missing from the booted list, package discovery is likely disabled or the package is not installed for the current PHP version.
- Can I use sledgehammer/core outside of Laravel in a plain PHP project?
- The package is described as serving Laravel and PHP projects, so some of its shared code may be framework-agnostic. The integration points it provides, however, are tied to Laravel conventions such as service providers and container bindings. Verify the actual dependencies in composer.json before assuming it will work in a non-Laravel application.
- Where can I find the source code, README, or report issues for sledgehammer/core?
- The repository URL is not listed in the package metadata provided here, so look at the support and homepage fields of the package on Packagist, or open the installed package directory and check its composer.json. That file usually names the source repository and the issue tracker. Use that channel for bug reports and pull requests rather than filing against your own application.
- How is sledgehammer/core maintained, and should I use it in production?
- As a foundational package, its releases follow the versioning of the wider Sledgehammer ecosystem, so check the tagged releases and changelog on Packagist and the source repository before adopting it. Pin a specific version in composer.lock, review changes between tags, and run your own test suite after upgrading. There is no public stability or maintenance guarantee stated in the metadata here, so treat it like any smaller ecosystem dependency and assess the release history yourself.
Weaver
How can I help you explore Laravel packages today?