glhd / composer-history
Installs: 1
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 3
Forks: 0
Open Issues: 0
Type:composer-plugin
Requires
- php: >=7.3
- composer-plugin-api: ^1.1
- ext-json: *
Requires (Dev)
- composer/composer: ^1.10
README
Quickly see the composer commands you've run on your current git branch.
Any time you run:
composer require
composer update
composer remove
It will be stored to a .composer-history
file in your project. You can run
the composer show-history
command to see all the history for your current
git branch, and run composer show-history --executable
to get a block of
text that you can copy and run to re-run your history.
This often is much easier than dealing with composer.lock
conflicts, as
you almost always want to just install an package or update one or two and
not affect any other changes that happened upstream.
Usage
$ composer require internachi/modular Loading composer repositories with package information Updating dependencies (including require-dev) ... $ composer update laravel/framework ... $ composer show-history Command history for feature/history-demo [2020-07-10 10:00:00] composer require internachi/modular [2020-07-10 10:01:00] composer update laravel/framework $ composer show-history --executable Command history for feature/history-demo composer require internachi/modular \ && composer update laravel/framework