- What is idmarinas/composer-plugin used for?
- idmarinas/composer-plugin is a lightweight Composer plugin that adds custom commands and event hooks to Composer itself. It is aimed at streamlining Laravel and general PHP package development by automating repetitive tasks during install, update, and post-autoload workflows. It registers automatically after installation and is described as having no runtime dependencies.
- How do I install idmarinas/composer-plugin in a Laravel project?
- Install it with Composer using composer require idmarinas/composer-plugin. Because it is a Composer plugin, it registers itself automatically after installation, so there is no Laravel service provider to add. On Composer 2.2 and newer you may need to allow the plugin in your project's allow-plugins configuration, depending on your Composer policy.
- Which Laravel, PHP, and Composer versions are supported?
- The provided documentation does not list specific Laravel, PHP, or Composer version constraints; it describes the plugin as framework-agnostic PHP with Laravel-friendly conventions. Check the package's composer.json require section and recent release history for the exact supported ranges before upgrading. Because it runs inside Composer rather than your application runtime, Laravel version coupling should be limited to any Laravel-specific commands or hooks you enable.
- What custom Composer commands does this plugin provide?
- The overview mentions custom Composer commands for common package maintenance tasks but does not enumerate them. After installation, run composer list to see the commands the plugin exposes in your project. Review the package README or source for each command's options before using it in shared scripts or CI.
- Which Composer events and hooks does idmarinas/composer-plugin support?
- The plugin plugs into Composer's event system, with the overview naming install, update, and post-autoload workflows. Those events can be used to automate tasks such as publishing assets, syncing configuration, or running post-install scripts. Confirm exact event names and configuration options against the README for the version you install.
- Is idmarinas/composer-plugin safe to use in production and CI builds?
- The package is described as PSR-compliant, framework-agnostic PHP with no runtime dependencies, so it should not add libraries to your application's runtime stack. Its work happens during Composer operations such as install and update, which typically means local development, build, or CI environments. As with any Composer plugin, review what it executes and pin a tested version in production build pipelines.
- How is idmarinas/composer-plugin different from Composer's built-in scripts?
- Composer's native scripts let you define commands in a project's composer.json for that project. This plugin extends Composer itself with packaged custom commands and event hooks aimed at reusable package maintenance workflows. For simple project-specific tasks, native scripts may be enough; use the plugin when you want reusable automation around install and update.
- Can I use idmarinas/composer-plugin outside Laravel in a plain PHP project?
- Yes. It is described as framework-agnostic, PSR-compliant PHP with no runtime dependencies, and it integrates with Composer rather than Laravel's container. The Laravel-friendly conventions are a convenience, not a requirement. Plain PHP Composer projects can use the same install, update, and post-autoload automation.
- How do I test the plugin before rolling it out?
- Try it in a throwaway Composer project or a CI branch and run install and update with verbose output so you can see which hooks fire. Use Composer's dry-run options where available and review any scripts the plugin adds before enabling them on shared branches. Because the overview does not list every hook, verify behavior against the README for the exact version you install.
- Is idmarinas/composer-plugin actively maintained?
- The provided overview does not include maintenance status, release cadence, or a repository link, so verify activity on Packagist and the source repository before adopting it. Check the latest release date, open issues, and compatibility with your Composer version. Pinning a tested version is prudent for build pipelines until you confirm ongoing maintenance.