- What is tey/concierge used for in a Laravel application?
- Tey Concierge is described as a lightweight package for building concierge-style service layers, coordinating requests, handlers, and workflows behind a clean API. It is also positioned as a standard suite of essentials for every Laravel app, so its scope may extend beyond orchestration alone. Treat it as an opinionated bundle and audit exactly which providers, helpers, and configuration it adds before adopting it.
- How do I install tey/concierge with Composer?
- Installation is a standard composer require tey/concierge, with Laravel package auto-discovery handling provider registration. The important step is verifying what gets registered: run composer why tey/concierge and composer audit, then diff the published config and provider list against a clean Laravel skeleton. Mechanical installation is easy, but the audit is where the real integration work happens.
- Which Laravel and PHP versions does tey/concierge support?
- The provided overview does not state explicit Laravel or PHP version constraints, so check the package composer.json on Packagist or GitHub before committing. Compare those constraints against your standard, such as PHP 8.2 or 8.3 and the current Laravel major. If the package lags the current Laravel release, that is an upgrade liability from day one and should disqualify it for new builds.
- Is tey/concierge a metapackage or does it contain first-party code?
- The description calls it a standard suite of essentials, but the overview does not clarify whether it is a thin metapackage or a code-bearing package. Inspect composer.json, the src directory, and the registered service providers to determine which it is. This distinction matters because a metapackage is low risk and easy to unwind, while code that replaces framework extension points creates high coupling and expensive removal.
- What service providers and facades does tey/concierge register?
- The provided overview does not document the boot behavior, facades, aliases, global helpers, or published configuration. The practical way to find out is to install it in an isolated spike branch and diff the registered providers and config files against a clean Laravel skeleton. Check specifically for global helpers or aliases that could collide with packages already in your application.
- Can I use tey/concierge in an existing Laravel application?
- It is a poor fit for an established application that already has settled conventions for logging, responses, auth scaffolding, or base models. The viable path is a greenfield or isolated service: create a spike branch, install the package, run composer audit, and diff published config and registered providers against a clean skeleton. That diff is effectively the integration contract, and it tells you whether adoption is realistic.
- How do I test a Laravel app that uses tey/concierge?
- The overview does not document testing helpers, so assume you will test through the package's public API rather than internal shortcuts. Write feature tests around your handlers and workflows, and use Laravel's container to swap in fakes for external dependencies. Also check whether the repository has a CI matrix across supported Laravel and PHP versions and what test coverage it reports.
- Is tey/concierge safe for production use?
- It is unproven in the wild, with no dependents or issue history, so you would be the first production adopter and would diagnose any defect yourself. It is also a single-organization package with a bus-factor-of-one risk, and the reported last release date appears to be in the future, which should be verified against tag provenance. Audit the transitive dependency graph, pin versions, and confirm the release is a real published artifact before relying on it.
- How do I remove tey/concierge if I no longer need it?
- Removal cost depends entirely on whether the package only adds opt-in utilities or leaves base classes, database assumptions, config files, and aliases behind. Composer remove is the easy part; afterward, diff your application against a clean skeleton and search for inherited classes and global helpers. If it is code-bearing rather than a thin metapackage, budget for a refactor rather than a clean uninstall.
- What are alternatives to tey/concierge for service layers in Laravel?
- The provided overview does not name alternatives, so evaluate single-purpose packages or framework-native patterns such as service classes, action classes, pipelines, and queued jobs. If tey/concierge is a bundle, its constituents may be replaceable individually, and cherry-picking is often safer than adopting the whole suite. Prefer alternatives with an active release cadence, a documented backward-compatibility policy, and a visible CI matrix.