Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Laravel Client

Laravel Client Laravel Package

1pilotapp/laravel-client

Laravel client for 1PilotApp that simplifies API integration in PHP applications. Provides a clean, configurable wrapper for authentication, requests, and responses so you can connect your Laravel app to 1PilotApp faster with less boilerplate.

View on GitHub
Deep Wiki
Context7

1Pilot.io, a universal dashboard to effortlessly manage all your Laravel applications

Frequently asked questions about Laravel Client
What is 1pilotapp/laravel-client used for?
It is the Laravel client for 1Pilot.io, a universal dashboard for managing Laravel applications. The package wraps API integration so you get a clean, configurable layer for authentication, requests, and responses. That means less boilerplate when connecting a Laravel app to 1PilotApp.
How do I install 1pilotapp/laravel-client with Composer?
Install it as a Composer dependency, typically with composer require 1pilotapp/laravel-client. Pin a specific version such as 1.0.14 during evaluation and confirm resolution in a non-production environment first. Review the package's composer.json for required PHP and Laravel constraints before rolling out.
Does 1pilotapp/laravel-client support Laravel 13?
Yes, release 1.0.14 is a compatibility patch whose only disclosed change is Laravel 13 support. No breaking changes, deprecations, or API changes are stated in that release note. Verify the supported Laravel and PHP matrix in composer.json and the CI configuration.
How do I configure the 1Pilot client in a Laravel application?
The package is described as a configurable wrapper for authentication, requests, and responses, so expect configuration for API credentials and client behavior. Check the repository README and any published config file for exact key names and environment variables. Confirm whether config publishing and a service provider are required for your setup.
Which Laravel and PHP versions does 1pilotapp/laravel-client support?
The 1.0.14 release adds Laravel 13 support, but the full supported matrix is not listed in the release note. Read the package's composer.json constraints and CI matrix to confirm which Laravel and PHP versions are covered. Also check whether adding Laravel 13 dropped support for older majors.
Is 1pilotapp/laravel-client 1.0.14 a breaking change?
No breaking changes or deprecations are disclosed; it is a patch release focused on Laravel 13 compatibility. Patch versioning suggests low migration effort for applications already on supported versions. Still run your test suite, because major framework upgrades can expose removed framework APIs and dependency conflicts.
How do I upgrade to 1pilotapp/laravel-client 1.0.14 safely?
Pin 1.0.14 in a staging or non-production environment, validate Composer resolution, and run your unit, integration, and regression tests. If you are also upgrading the application to Laravel 13, validate both changes together with a rollback plan. Canary deploy before completing the rollout.
Does 1pilotapp/laravel-client have tests for Laravel 13?
The release note does not state whether Laravel 13 is part of the package's CI matrix. Inspect the repository's CI configuration to see which Laravel and PHP combinations are tested. Ask maintainers whether service provider, config, migrations, and package integrations are exercised against Laravel 13.
Can I just use Laravel's HTTP client instead of 1pilotapp/laravel-client?
You can call the 1Pilot API directly with Laravel's HTTP client or Guzzle if you only need a few endpoints. The package's value is a configurable wrapper that centralizes authentication, request, and response handling to reduce boilerplate. Choose it when you want consistent integration behavior rather than hand-rolled calls.
What are the risks of adopting 1pilotapp/laravel-client in production?
Risks include Composer dependency conflicts, untested Laravel 13 integration paths, and silent behavior changes if CI coverage is thin. Support gaps matter too if Laravel 13 is claimed but not actively maintained. Vet the changelog, support policy, and maintainer responsiveness before promoting to production.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
robertmarney/lara-hierarchial-collections
simonschaufi/rule-doc-generator
emissaoja/emissaoja
blackbricksoftware/gravityforms-civicrm-form-processor
al-rahabi/fancy-crud
jinas/dhivatar-component
mltstephane/laravel-quality
bernskiold/laravel-talentlms
bernskioldmedia/laravel-form-architect
youbar/easy-crud
c-point-labs/laravel-hostyourai
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo