- What is seatplus/core used for?
- seatplus/core is the core foundation for Seatplus, a Laravel-based EVE Online management platform. It supplies the shared services, ESI integration, and the base models and contracts that other Seatplus packages build on. In practice you use it when you want to extend Seatplus without reimplementing its plumbing yourself.
- How do I install seatplus/core with Composer?
- Install it with composer require seatplus/core. Because it is a foundation package, it is often already pulled in as a dependency of other Seatplus packages, so check your composer.json before adding it explicitly. Review the repository README for any service provider registration or migration steps required in your Laravel app.
- Which Laravel versions does seatplus/core support?
- Laravel version support is defined by the constraints in the package's composer.json, so check that file on GitHub or Packagist before installing. Match those constraints against the Laravel version in your application to avoid dependency conflicts. If you are on an older Laravel release, verify compatibility before planning an upgrade path.
- Do I need to install seatplus/core directly to use other Seatplus packages?
- Usually not. Composer resolves seatplus/core automatically when another Seatplus package requires it, so most applications get it transitively. Install it explicitly only when you are building your own package or module that depends directly on its contracts, base models, or shared services.
- What does ESI integration in seatplus/core mean?
- ESI is EVE Online's HTTP API, and seatplus/core provides the shared ESI integration layer used across the Seatplus platform. That means ESI-related concerns live in one place rather than being reimplemented by every package. Building on this layer keeps your own Seatplus extensions consistent with the rest of the ecosystem.
- Can I build my own package on top of seatplus/core?
- Yes, that is exactly what the package is designed for. Require seatplus/core in your package's composer.json and build against its base models, contracts, and shared services instead of duplicating platform plumbing. Following its contracts also keeps your extension compatible with future changes in the Seatplus ecosystem.
- Is seatplus/core a standalone application or a library?
- It is a Composer library, not a turnkey application. It provides the shared foundation that the Seatplus platform and its other packages depend on, rather than a ready-to-use EVE Online management front end. If you need the full platform, look at the Seatplus application repositories rather than core alone.
- How do I test a Laravel package that depends on seatplus/core?
- Run your tests inside a Laravel test application or Orchestra Testbench so the core service providers and configuration are available. Register the providers your package needs and assert behaviour against the contracts and base models that core defines. Check the repository's own test setup for the conventions the maintainers use.
- How is seatplus/core maintained and where do I report issues?
- The package lives in the Seatplus organisation on GitHub, so use the repository's issue tracker for bug reports and feature requests, and pull requests for contributions. Review the release history and commit activity on GitHub or Packagist to judge how actively it is maintained before adopting it. Pinning versions in composer.json is wise for production applications.
- What are the alternatives to seatplus/core for EVE Online apps?
- If you only need to talk to EVE's ESI API, a standalone ESI client library or a generic OAuth2 package may be enough, and you can build your own models on top. However, there is no drop-in replacement for the shared models, contracts, and services that seatplus/core provides to the Seatplus ecosystem. Choose core when you want to extend Seatplus rather than start from scratch.