neronmoon / scriptsdev
Scripts-dev behaviour for Composer
Installs: 1 175 417
Dependents: 33
Suggesters: 0
Security: 0
Stars: 69
Watchers: 3
Forks: 5
Open Issues: 1
Type:composer-plugin
Requires
- composer-plugin-api: ^1.0 || ^2.0
Requires (Dev)
- composer/composer: ~1.0@dev || ~2.0@dev
This package is auto-updated.
Last update: 2024-10-16 16:00:45 UTC
README
It's like require-dev, but for scripts
Installation
Just run composer require neronmoon/scriptsdev --dev
Usage
After installing you able to add extra.scripts-dev directive in your composer.json
... "extra": { "scripts-dev": { "post-install-cmd": [ "npm install --dev" ], "post-update-cmd": "php ./someCoolCommand.php", "test": "phpunit" }, } ...
Deprecated Usage
... "scripts-dev": { "post-install-cmd": [ "npm install --dev" ], "post-update-cmd": "php ./someCoolCommand.php" } ...
Known issues
- Usage of this plugin will cause minor warning of validation process.
composer validate
command will display something like this.
./composer.json is valid, but with a few warnings
See https://getcomposer.org/doc/04-schema.md for details on the schema
Description for non-existent script "test" found in "scripts-descriptions"