About the post-install-cmd example and installing with --no-dev · Issue #100 · BrainMaestro/composer-git-hooks · GitHub
![Nuno Maduro 🤌🏻 on Twitter: "The composer scripts section is a lovely way to combine the multiple commands of your test suite. In this example, a simple “composer test” runs the entire Nuno Maduro 🤌🏻 on Twitter: "The composer scripts section is a lovely way to combine the multiple commands of your test suite. In this example, a simple “composer test” runs the entire](https://pbs.twimg.com/media/EGgQAqkXUAAzoaZ.jpg)
Nuno Maduro 🤌🏻 on Twitter: "The composer scripts section is a lovely way to combine the multiple commands of your test suite. In this example, a simple “composer test” runs the entire
![laravel - "php artisan myCommand" handling the post-install-cmd event returned with error code 1 - Stack Overflow laravel - "php artisan myCommand" handling the post-install-cmd event returned with error code 1 - Stack Overflow](https://i.stack.imgur.com/N5Pdz.png)
laravel - "php artisan myCommand" handling the post-install-cmd event returned with error code 1 - Stack Overflow
![nystudio107 on Twitter: "✓ Craft CMS 3 tip: Did you know that composer can execute scripts/commands, just like npm can? So you could have Craft migrations run automatically after a `composer update` nystudio107 on Twitter: "✓ Craft CMS 3 tip: Did you know that composer can execute scripts/commands, just like npm can? So you could have Craft migrations run automatically after a `composer update`](https://pbs.twimg.com/media/DtK_uk0WkAAh9t4.png)