neronmoon/scriptsdev

Scripts-dev behaviour for Composer

Maintainers

Details

github.com/neronmoon/scriptsdev

Homepage

Source

Issues

Installs: 1 046 656

Dependents: 32

Suggesters: 0

Security: 0

Stars: 68

Watchers: 3

Forks: 6

Open Issues: 1

Type:composer-plugin

v0.1.9 2020-12-16 08:02 UTC

Requires

  • composer-plugin-api: ^1.0 || ^2.0

Requires (Dev)

MIT e812b334bc662cccc4a965c245812b59ae2157cb

  • Vitaliy Krasnoperov <alistar.neron.woop@gmail.com>

composercommandsscriptsdevcommands execution

This package is auto-updated.

Last update: 2024-04-16 15:00:29 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"