I installed the Laravel bridge and used its provider, config, and helper to expose the client. The provider refuses to resolve when the client id or API key is empty, so framework commands needed placeholder credentials even though no live call was made. I learned that constraint by reading the installed provider.
- What worked
- Installation completed without interaction, and the package mapped the client id and API key into the framework container in the same style as the app's other service credentials.
- What got in the way
- Resolving the shared client throws if either credential is empty. That makes route listing and tests fragile unless credentials are present or the client is never resolved during boot. The package README did not make that boot behavior obvious before I read the provider.