Weave Code
Composer Compile Plugin Laravel Package
civicrm/composer-compile-plugin
Composer plugin that adds a lightweight compile step for CiviCRM extensions and other PHP packages. Declare compile tasks in composer.json and it runs them after install or update, skipping unchanged packages via caching. A composer compile command allows manual rebuilds.
Allow composer packages to define compilation steps
Frequently asked questions about Composer Compile Plugin
- What does the civicrm/composer-compile-plugin do?
- It is a Composer plugin that lets packages declare compilation steps in composer.json and runs them after Composer install or update. It also provides a composer compile command for manual rebuilds and uses caching to skip packages that have not changed. It is a build and dependency-layer tool, not a Laravel runtime package.
- How do I install civicrm/composer-compile-plugin in a Composer project?
- Install it as a Composer dependency and explicitly allow it in Composer 2's allow-plugins configuration, because Composer plugins execute code during dependency operations. Pin a version or commit while you evaluate it. The provided context does not include exact installation commands, so verify them against the upstream source before standardizing.
- Is this package compatible with Laravel?
- Laravel version is mostly irrelevant here; the real constraints are PHP and Composer compatibility. It can sit in Laravel build or CI workflows if you consume packages that need compile steps, but it should not be an application runtime dependency. Confirm Composer 2.x, supported PHP versions, and your CI matrix before adopting it.
- Does civicrm/composer-compile-plugin work with Composer 2?
- The technical evaluation says it is technically feasible on Composer 2 with explicit allow-plugins configuration. Whether it is Composer 2-only or supports older Composer versions is not confirmed in the provided context. Review the plugin source and upstream release history before relying on it.
- How does the compile step caching work?
- The overview says compile tasks run after install or update and that unchanged packages are skipped via caching. The exact cache key, invalidation rules, and whether outputs are deterministic are not documented in the provided context. Test caching behavior in an isolated branch and CI job before depending on it.
- Can I run compilation manually with composer compile?
- Yes, the package exposes a composer compile command for manual rebuilds. This is useful as a fallback when install or update hooks are skipped or blocked. Document the manual path so your team can reproduce compile steps without the plugin.
- What are the security risks of using a Composer plugin like this?
- Composer plugins execute code during install and update, which creates supply-chain and build-reproducibility risk. Low adoption signals such as 13 stars, a 0.495 score, and an unknown repository increase maintenance and provenance uncertainty. Do a source and security review, pin the dependency, and restrict plugin execution in CI.
- Does it work in CI and on Windows, macOS, and Linux?
- The provided context does not confirm cross-platform behavior, and compile steps may be platform-specific, non-idempotent, or dependent on external binaries. Validate it on a sample package across your target CI matrix before standardizing. Use build caching and deterministic outputs to keep CI time and complexity under control.
- Is civicrm/composer-compile-plugin maintained and safe for production?
- The upstream repository is unknown in the provided context, so current maintenance, release history, and security posture cannot be confirmed. The technical evaluation rates risk medium-high and recommends a conditional pilot for internal package compilation only. Production deployments should consume prebuilt artifacts rather than run compilation on application servers.
- What alternatives should I consider before adopting this plugin?
- For Laravel frontend assets, prefer Vite and npm; for package-level generated code, compare this plugin against existing Composer scripts. Use it only where it removes real duplication in package-specific compile steps. Keep Laravel asset compilation on its existing path and avoid making the plugin a critical single point of failure.
Weaver
How can I help you explore Laravel packages today?