VOOZH about

URL: https://deepwiki.com/invokable/laravel-boost-phpstorm-copilot/7.1-package-configuration-(composer.json)

⇱ Package Configuration (composer.json) | invokable/laravel-boost-phpstorm-copilot | DeepWiki


Loading...
Last indexed: 28 February 2026 (57ef88)
Menu

Package Configuration (composer.json)

This page is a full reference for composer.json1-84 covering the package's identity metadata, runtime and development dependency constraints, PSR-4 autoload maps, Laravel provider auto-discovery entry, and all defined Composer scripts.

For how the service provider registered here integrates with the Boost framework at runtime, see 4.4. For the testing infrastructure that several of these scripts drive, see 7.4 and 6.1.


Package Identity

composer.json1-10

FieldValue
namerevolution/laravel-boost-phpstorm-copilot
descriptionLaravel Boost Custom Agent for PhpStorm with GitHub Copilot plugin
typelibrary
licenseMIT
keywordslaravel, boost, phpstorm, github-copilot

The type: library designation means Composer treats this as a reusable package with no executable entry point of its own.

Sources: composer.json1-10


Runtime Dependencies (require)

composer.json12-16

PackageConstraintPurpose
php^8.3Minimum PHP version; uses modern type system features
illuminate/support^12.30||^13.0Laravel service provider base class and framework utilities
laravel/boost^2.0Agent abstraction, SupportsMcp, SupportsGuidelines, SupportsSkills interfaces, and the boost:mcp / boost:install Artisan commands

The double constraint on illuminate/support (^12.30||^13.0) allows the package to work with both the current and the next major Laravel release cycle.

Sources: composer.json12-16


Development Dependencies (require-dev)

composer.json17-24

PackageConstraintRole in development
laravel/pint^1.25Code style enforcement (PSR-12 + strict rules); see 6.3
orchestra/testbench^10.6Laravel application harness for package testing; provides vendor/bin/testbench
pestphp/pest^4.1Test runner
pestphp/pest-plugin-laravel^4.0Pest integration for Laravel-specific assertions
mockery/mockery^1.6Mocking library used in detection strategy tests
revolution/laravel-boost-copilot-cli^2.0Copilot CLI agent used in the workbench development environment

None of the require-dev packages are shipped to end users who composer require this package.

Sources: composer.json17-24


Autoloading

Production Autoload Map

composer.json25-29

PSR-4 namespace: Revolution\Laravel\Boost\
Root directory: src/

All production classes — PhpStormCopilot, PhpStormCopilotServiceProvider, and Concerns\WithWSL — live under src/ and are resolved via this single namespace prefix.

Development Autoload Map

composer.json30-36

NamespaceDirectoryContents
Tests\tests/Pest test files
Workbench\App\workbench/app/Workbench application classes
Workbench\Database\Factories\workbench/database/factories/Model factories for the workbench app
Workbench\Database\Seeders\workbench/database/seeders/Database seeders for the workbench app

Sources: composer.json25-36


Laravel Provider Auto-Discovery

composer.json47-53

The extra.laravel.providers array tells Laravel's package auto-discovery mechanism to load PhpStormCopilotServiceProvider automatically when the package is installed into a Laravel application, without any manual registration in config/app.php.


When Composer runs post-autoload-dump, Laravel reads this entry and adds the provider to the discovered packages manifest. The provider's boot() method then calls Boost::registerAgent('phpstorm-copilot', PhpStormCopilot::class). See 4.4 for full details.

Autoload and discovery flow:


Sources: composer.json47-53


Composer Scripts

composer.json55-78

All scripts are defined under the scripts key and invoked with composer <name>.

ScriptCommand(s)Purpose
testpestRun the full Pest test suite
test:coveragepest --coverage --coverage-clover build/logs/clover.xmlRun tests with Xdebug coverage and emit a Clover XML report
lintpintApply Laravel Pint code style fixes in-place
test:lintpint --testCheck code style without modifying files (non-zero exit on violation)
boostvendor/bin/testbench boost:install --no-interaction --ansiRun the Boost install wizard inside the testbench workbench
clear@php vendor/bin/testbench package:purge-skeleton --ansiRemove generated workbench skeleton files
prepare@php vendor/bin/testbench package:discover --ansiRe-run package discovery for the workbench app
build@php vendor/bin/testbench workbench:build --ansiCompile workbench assets and scaffold
serve@build + @php vendor/bin/testbench serve --ansiBuild and start a local HTTP server for the workbench app
post-autoload-dump@clear, @prepare, @buildAutomatically refresh the workbench after every composer install or composer dump-autoload

The post-autoload-dump hook means that after any dependency change (composer install, composer update, composer dump-autoload), the workbench is always left in a clean, ready state without manual intervention.

Script dependency graph:


Sources: composer.json55-78


Plugin Permissions

composer.json79-83


Composer requires explicit opt-in for plugins that execute code during the install process. The pestphp/pest-plugin entry authorises the Pest plugin system to register itself during composer install.

Sources: composer.json79-83


Dependency Constraint Summary


Sources: composer.json12-24