sweetchuck / composer-suite-cli
Generates alternative composer.*.json files without any requirements.
Installs: 1
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 3
Forks: 0
Open Issues: 1
Type:project
Requires
- php: >=7.4
- ext-json: *
- psr/log: ^1.1
- sweetchuck/composer-suite-handler: ^1.0
- symfony/console: ^5.1 || ^6.0 || ^7.0
- symfony/dependency-injection: ^5.3 || ^6.0 || ^7.0
- symfony/filesystem: ^5.4 || ^6.0 || ^7.0
Requires (Dev)
- codeception/codeception: ^4.1
- codeception/module-asserts: ^1.3
- codeception/module-cli: ^1.1
- consolidation/robo: ^3.0
- mikey179/vfsstream: ^1.6
- nuvoleweb/robo-config: 2.x-dev
- phpstan/phpstan: ^1.5
- phpstan/phpstan-symfony: ^1.1
- squizlabs/php_codesniffer: ^3.6
- sweetchuck/git-hooks: 2.x-dev
- sweetchuck/robo-composer: 2.x-dev
- sweetchuck/robo-git: 2.x-dev
- sweetchuck/robo-phpcs: 2.x-dev
- sweetchuck/robo-phpstan: 1.x-dev
- symfony/error-handler: ^5.3 || ^6.0 || ^7.0
- symfony/finder: ^5.3 || ^6.0 || ^7.0
README
Note that the Composer Suite and Composer Suite CLI projects are different
projects.
Composer Suite is a Composer plugin.
Composer Suite CLI is an individual CLI tool.
Both projects have the same goal, but the method they work is different.
The easiest way to work with the Composer Suite Composer plugin is that,
when the plugin is already added to the requirements (require-dev or
require).
If that is not the case, then the workarounds aren't obvious and
intuitive.
For example you are working on a third-party project to fix bugs or add new features, and you need to overwrite something (e.g.: minimum PHP version) in the composer.json, or add extra developer helper packages, but those modifications aren't part of the scope, then this „Composer Suite CLI” tool comes into play.
The „Composer Suite CLI” reads the configuration from the same sources as the „Composer Suite” plugin does it, but this is an individual CLI tool.