- Can I install tefps/clients-bundle in a Laravel application?
- Yes, Composer will install it, but the package ships as a Symfony bundle and will not boot on its own in Laravel. Treat it as a vendored library: instantiate the underlying client from a Laravel service provider and bind it as a singleton. Keep the bundle registration class out of the picture entirely.
- Does tefps/clients-bundle support Laravel 10 or 11?
- There is no official Laravel support or documented Laravel version compatibility for this Symfony-first package. Real compatibility depends on the Symfony component pins and PHP version floor resolving against your Laravel app. Validate by pinning an exact version or commit hash and running your test suite during a spike.
- How do I register the TEFPS client in Laravel's service container?
- Create a dedicated Laravel service provider that instantiates the underlying client and binds it as a singleton. Wrap it behind your own narrow interface, such as TefpsDeclarationGateway, so vendor DTOs do not leak into controllers, jobs, or models. Register config under config/tefps.php and keep credentials in your secret store.
- Is tefps/clients-bundle safe to use in production?
- The technical risk is high because the package shows 0 stars, 0 dependents, and no observable maintenance cadence. On a regulatory filing path, a silent upstream API change could break statutory declarations rather than just a UI. Feature-flag the integration, keep manual filing as fallback, and validate in shadow mode before live submissions.
- What PHP version does tefps/clients-bundle require?
- The provided context warns that a 7.x PHP target may install on PHP 8.x but is untested there, so the exact floor should be verified from the package's composer.json. Run your application test suite against PHP 8.x with deprecations promoted to errors during the spike. That surfaces the true constraint surface early.
- How does tefps/clients-bundle authenticate with the TEFPS API?
- The auth model is undocumented in the available assessment: it is unclear whether it uses an API key or OAuth2 client credentials. Validate this against a supported sandbox and credential set before committing. Do not assume retry or idempotency semantics, because none are published.
- Can I use tefps/clients-bundle without Symfony?
- You cannot use the Symfony bundle lifecycle, but the client core may be separable from the bundle. The key question is whether DI wiring is load-bearing or whether business logic lives inside DI-configured services. If it does, you would be reimplementing wiring by hand, which changes the estimate.
- Will tefps/clients-bundle conflict with Laravel's Symfony components?
- There is a real risk that the package's Symfony component version pins conflict with Laravel's transitive symfony/* set. Pin by exact version, or by commit hash if no tags exist, and commit the lockfile. Assume no semver discipline and resolve Composer in an isolated spike first.
- How should I test the TEFPS integration in a Laravel app?
- Start with an isolated spike in a scratch branch: install the package, resolve Composer, authenticate to sandbox, and execute one read and one write. Wrap the client behind your own domain-shaped interface and test that adapter. Then run shadow-mode filings that compute payloads without submitting before limited production submission.
- What licence does tefps/clients-bundle use, and can I fork it?
- Licence clarity for forking is listed as an open question in the assessment, so confirm the licence before relying on the package. If forking is permitted, self-maintaining a contained copy may be safer than depending on an unmaintained upstream. Also confirm who owns the TEFPS API contract and whether this client is officially sanctioned.