Weave Code
Tds Provider Bundle Laravel Package
firelink-media/tds-provider-bundle
A Laravel bundle that packages TDS provider integrations into one installable service provider. It registers bindings, config, and auto-discovery so you can wire TDS services into your app quickly, with sensible defaults and an extensible structure for adding custom providers.
TDS Provider Bundle
firelink-media/tds-provider-bundle is a Laravel package that bundles TDS service providers into a single, installable dependency. Instead of wiring multiple providers by hand, drop this package in and let Laravel's package auto-discovery register everything for you—keeping your config/app.php clean and your TDS integration consistent across projects.
It follows Laravel conventions with PSR-4 autoloading, publishable configuration, and straightforward extensibility, making it easy to install, configure, and maintain.
- One-line Composer installation with automatic provider registration
- Publishable configuration for environment-specific TDS settings
- Laravel auto-discovery support—no manual provider wiring
- Clean PSR-4 structure ready for extension
- Compatible with modern Laravel releases
Frequently asked questions about Tds Provider Bundle
- Is firelink-media/tds-provider-bundle compatible with Laravel?
- Not confirmed. The package name and the Bundle suffix point to a Symfony-origin integration, and the overview does not state that it ships a Laravel ServiceProvider or extra.laravel.providers auto-discovery. Treat it as a Symfony bundle that may need a hand-written bridge, and inspect composer.json before planning the integration.
- How do I install and register the TDS provider bundle in a Laravel app?
- Install it with composer require firelink-media/tds-provider-bundle, publish any shipped configuration, and supply credentials through environment variables rather than a committed config file. If auto-discovery is absent you must register the vendor binding manually in a dedicated service provider. Document that manual step so it is not lost during framework upgrades.
- Which PHP and Laravel versions does the TDS provider bundle support?
- The overview does not publish a version matrix, so you need to inspect the illuminate/* and php constraints in composer.json yourself. Pin the package to an exact minor and run CI against the lowest and highest Laravel versions you support. Also watch for symfony/* version pins that can conflict with your existing lockfile.
- What license does the TDS provider bundle use, and is GPL-3.0 safe for a commercial Laravel app?
- The package is GPL-3.0. For an internal-only SaaS this is usually tolerable, but if you distribute the application as a self-hosted or on-prem install, copyleft obligations may attach to the combined work. Treat legal review as a gate before adoption rather than a checkbox.
- How do I keep TDS credentials secure and rotate them?
- Keep credentials in environment variables backed by a secrets manager and never in a published config file. The overview does not document the auth model, token lifetime, or refresh semantics, so confirm those with the vendor before going live. Build rotation into your deployment process rather than hard-coding long-lived tokens.
- Can I swap or combine multiple TDS providers with this bundle?
- The bundle advertises a provider abstraction and configuration-driven setup, which is the main reason to use it over raw HTTP calls. Bind it behind an internal interface you own, such as TdsProvider, so domain code never imports vendor classes. That preserves the option to swap providers or replace the package with direct API calls later.
- Is firelink-media/tds-provider-bundle actively maintained and production ready?
- Signals are thin: zero stars, zero known dependents, a single vendor, and one dated release, so upstream abandonment is a live scenario. Test coverage, CI status, and a breaking-change policy are not documented. Assume you own the regression suite around the integration and pin the exact version.
- How should I test a TDS integration in a Laravel test suite?
- Bind a fake implementation of your own TdsProvider interface in tests so feature tests never hit the live TDS service. Add contract tests that run against a vendor sandbox tenant if one exists. If you already have a bespoke client, run a shadow period that calls both implementations and diffs the normalized output before cutting reads over.
- Will the bundle conflict with Guzzle or Symfony packages already in my lockfile?
- Possible. The package may pin symfony/* components or guzzlehttp/guzzle in ways that conflict with your existing constraints, so check for conflicts before merging. Add a lockfile-diff check so an incidental composer update cannot silently change the vendor transport layer.
- What are the alternatives if the package is abandoned or GPL-3.0 is a blocker?
- Treat the package as an anti-corruption layer rather than a hard dependency: define your own port interface first and let the bundle be one implementation behind it. If licensing or maintenance degrades, swap in a thin HTTP client you control without touching domain code. If the package turns out to be only a thin wrapper, wrapping the raw TDS API yourself is often the cheaper path anyway.
Weaver
How can I help you explore Laravel packages today?