Weave Code
Esplora Laravel Package
esplora/esplora
Esplora is a Laravel package that lets you explore and inspect your application's structure and data through a clean, developer-friendly interface. It installs in minutes, fits naturally into existing projects, and helps you understand what's happening under the hood.
Esplora is an open-source package for @Laravel with which you can easily collect visitor analytics.
Frequently asked questions about Esplora
- How do I install esplora/esplora in a Laravel application?
- Install it with Composer using composer require esplora/esplora. Laravel's package discovery should register the service provider and facade automatically. For version 0.0.x, pin the exact release in composer.json rather than using a floating constraint, because there is no SemVer compatibility guarantee.
- Can I use esplora/esplora without Laravel?
- Yes. The package integrates with Laravel through a service provider and facade, but it is also designed to remain usable in standalone PHP projects. In standalone use you instantiate and configure the client yourself instead of resolving it from Laravel's container.
- What Bitcoin blockchain data can I query with esplora/esplora?
- The client covers blocks, transactions, addresses, and UTXOs, plus mempool activity and recommended fee estimates. It also supports retrieving address histories and balances and broadcasting signed Bitcoin transactions. It is a client for the Blockstream Esplora REST API, so it does not store blockchain data itself.
- Which Laravel and PHP versions are supported by esplora/esplora?
- The package overview does not document a supported Laravel or PHP version matrix, and the technical assessment flags version support as unverified. Check the composer.json constraints in the repository against your application's pinned Laravel and PHP versions before adopting it. If the constraints do not match, the evaluation can end there without further work.
- Is esplora/esplora safe for production at version 0.0.9?
- Treat 0.0.9 as pre-1.0: 0.0.x releases carry no SemVer compatibility guarantee, so breaking changes can appear in any release. There are no 0.0.9 release notes, which means upgrade risk cannot be assessed from a changelog. Pin the exact version and wrap the package behind your own interface so a future package swap is not a refactor.
- What changed between esplora/esplora 0.0.8 and 0.0.9?
- The 0.0.9 release provides no release notes, only a diff link for 0.0.8...0.0.9. That makes the change set undisclosed in the artifact, so you must read the diff and commit history yourself. If the diff includes signature changes, treat 0.0.9 as a 0.1.0-class change and re-baseline your assumptions.
- Does esplora/esplora use Blockstream's public Esplora API or a self-hosted server?
- The package is a client for the Blockstream Esplora REST API, and your application must decide which Esplora endpoint it points at. That can be Blockstream's public instance or a self-hosted Esplora server. Relying on a hosted endpoint couples production reliability to an API you do not operate and whose rate limits and schema you do not control.
- Does esplora/esplora return typed DTOs or raw JSON arrays?
- The overview does not state whether responses are typed DTOs or raw arrays, and the technical assessment flags response typing as unverified. Inspect the client code before building application logic around the return values. If it returns raw arrays, your code couples directly to the upstream JSON shape and becomes harder to migrate later.
- How do I broadcast a signed Bitcoin transaction using esplora/esplora?
- The package supports broadcasting signed Bitcoin transactions through the Esplora API. The exact method name is not given in the overview, so check the facade or client class in the installed version. Test broadcasts against testnet or signet before using mainnet.
- Should I use esplora/esplora or call the Esplora API with Laravel's HTTP client?
- A thin 1:1 transport wrapper adds little over Laravel's Http::get(), while an opinionated client with typed responses, pagination, and an error taxonomy can justify the dependency. The overview positions esplora/esplora as a clean, expressive client, but the exact abstraction level is unverified. Either way, put an internal interface such as a ChainDataProvider in front of it so the package is replaceable.
Weaver
How can I help you explore Laravel packages today?