Weave Code
Cachelet Core Laravel Package
oxhq/cachelet-core
Core caching utilities for Laravel: a driver-agnostic cache layer with tagged entries, TTL helpers, remember-style callbacks, and consistent key generation. Provides the shared foundation for Cachelet packages and custom cache adapters.
Core cache orchestration runtime for Cachelet.
Frequently asked questions about Cachelet Core
- What is oxhq/cachelet-core used for?
- Cachelet Core is described as the core cache orchestration runtime for Cachelet. Its advertised capabilities include a driver-agnostic cache layer with tagged entries, TTL helpers, remember-style callbacks, and consistent key generation. It is intended to provide a shared foundation for Cachelet packages and custom cache adapters. The package is at v0.1.0 and does not yet publish API documentation or usage examples.
- How do I install oxhq/cachelet-core in Laravel?
- Install it with Composer using composer require oxhq/cachelet-core. Because the package has no documented service provider, config surface, or Laravel support matrix, first test the require in a disposable Laravel project and inspect what it registers. Do not assume auto-discovery or publishable configuration until you have verified the package source and composer.json.
- Which Laravel and PHP versions does cachelet-core support?
- No Laravel or PHP support matrix is documented in the available package information. Check the composer.json version constraints in the published package and confirm they match your application before adoption. Because this is a pre-1.0 release, the supported range may change without a deprecation cycle.
- Does cachelet-core work with Laravel's Cache facade and existing cache stores?
- That is the key integration question, and it is not documented. If Cachelet Core implements Illuminate\Contracts\Cache\Store, it could slot beneath Laravel's Cache facade with a configuration change. If it provides a parallel abstraction instead, adoption would mean a second cache tier or a wrapper layer you own and maintain.
- What are tagged cache entries and TTL helpers in Cachelet Core?
- The package overview advertises tagged cache entries, TTL helpers, remember-style callbacks, and consistent key generation. These are common caching conveniences for grouping related entries, controlling expiration, and memoizing expensive lookups. However, v0.1.0 ships without API documentation, so confirm method names and behavior from the source before relying on them.
- Is cachelet-core stable enough for production use?
- Cachelet Core is at v0.1.0, so the public API is explicitly pre-1.0 and may change in any 0.x minor release without a deprecation cycle. It is also a new package from a new organisation with no stated security policy or maintainer roster. Treat it as a watch-list item or evaluate it behind a feature flag rather than adopting it as a production dependency without due diligence.
- How does cachelet-core handle cache key generation and collisions?
- Consistent key generation is one of the advertised features, but the exact key format and namespacing rules are not documented. Namespace and key-space collisions with your existing cache keys cannot be verified without source inspection. Review the key-generation code and test against your existing cache keys before enabling it alongside an incumbent store.
- Can I use cachelet-core without other Cachelet packages?
- It is not clear that v0.1.0 is independently useful. The phrase core runtime suggests it may be a shared dependency for sibling Cachelet packages that are not yet released. If so, it delivers no end-user capability today and should be treated as a watch-list item rather than an adoption candidate.
- How should I test cachelet-core in a Laravel application?
- Use an additive, shadowable approach rather than a cutover. Install it in a disposable branch, wire it alongside your existing cache behind a feature flag, run dual-write with shadow reads, and compare hit rate, latency, and value fidelity over a representative traffic window. Because the package is pre-1.0, keep the change operationally reversible.
- What are the alternatives to cachelet-core, and who maintains it?
- Laravel's built-in Cache facade and established PSR-6 or PSR-16 cache packages are the obvious alternatives for most applications. Cachelet Core is published as a read-only split from the upstream monorepo at github.com/oxhq/cachelet, so fixes must go through that upstream repository rather than the package itself. Release cadence depends on upstream CI, and no accountable maintainer or security disclosure process is stated.
Weaver
How can I help you explore Laravel packages today?