- What does gioppy/statamic-aggregate-assets do?
- It is a Statamic addon that aggregates and bundles CSS and JavaScript assets, letting you manage front-end dependencies from one place and serve combined asset files in your templates. The goal is better front-end performance by reducing the number of separate asset requests. It is distributed as a Composer package and depends on Statamic, which runs on Laravel.
- How do I install gioppy/statamic-aggregate-assets?
- Install it with Composer using composer require gioppy/statamic-aggregate-assets, then confirm that the package service provider is auto-discovered by Laravel. Publish any optional configuration if the package provides it, and smoke-test the Statamic control panel to make sure the addon loads. Because the package is pre-1.0, pin an explicit version in your root composer.json instead of relying on an open constraint.
- Does this package support Laravel 11 and Statamic 5?
- Version 0.0.3 changed the Statamic constraint in composer.json from version 3.0 to an upper bound, but the literal constraint string matters and should be checked before assuming Statamic 5 support. Statamic 3, 4, and 5 map to very different Laravel and PHP baselines, so an open constraint alone is not proof of compatibility. Verify the actual package composer.json and test against the specific Statamic major you run.
- Which Statamic versions are actually tested in CI?
- The available technical evaluation does not show a documented CI matrix, and the 0.0.3 release note is a one-line change with no stated test coverage. That means the advertised constraint range may be broader than what has actually been exercised. Ask the maintainer which Statamic majors, PHP versions, and Laravel versions are tested, and add your own smoke tests for the major you use.
- Is the 0.0.3 release safe if it only changes composer.json?
- The 0.0.3 change is described as a packaging change that edits the Statamic constraint, not a code change, so existing locked installs should see little or no movement. However, the diff does not prove the code works across the newly permitted Statamic range. Treat it as a resolution-surface change: pin versions, run composer update --with-dependencies on a branch, and inspect the lockfile diff.
- How do I configure and use asset bundles in my templates?
- The addon is intended to let you define front-end dependencies in one place and then serve combined CSS and JavaScript files from Statamic templates. Installation typically involves publishing the package configuration if available, defining your bundles, and referencing them from Antlers or Blade templates. Check the package README or config file for the exact configuration keys and template syntax, since those details are not included in the provided excerpt.
- Is this package safe to use in production?
- The technical risk is moderate-to-high because the 0.0.3 constraint appears open-ended and the package is pre-1.0, so there is no stability contract. Production use should include explicitly pinning both statamic/cms and the package version in your root composer.json, committing the lockfile, and testing the control panel plus any custom fieldtypes, tags, or modifiers. Also verify that existing content round-trips correctly before deploying.
- What are alternatives to this Statamic asset aggregation addon?
- Common alternatives include Laravel's default Vite integration, Laravel Mix, or a manual front-end build pipeline that outputs combined CSS and JavaScript files. Statamic projects can also manage assets directly through their templates and theme structure without an addon. This package is most relevant if you specifically want Statamic-side aggregation and a single place to manage front-end dependencies.
- Who maintains gioppy/statamic-aggregate-assets and is it actively maintained?
- The provided evaluation does not establish a maintenance policy, a CI matrix, or a stated upper-bound strategy, and the 0.0.3 release has only a one-line note. Before adopting it, review the repository history, issue activity, and release cadence to judge maintenance health. If long-term support matters, ask whether the maintainer plans to cap Statamic compatibility with an explicit upper bound such as <6.0.
- How do I prevent Composer from pulling an unexpected Statamic major version?
- Pin the CMS and the addon explicitly in your root composer.json, for example with statamic/cms set to the major you actually run and gioppy/statamic-aggregate-assets pinned to 0.0.3. Then create a branch, run composer update --with-dependencies, and commit the resulting lockfile after reviewing what moved. Your application's composer.json, not the package's open constraint, should be the source of truth for the Statamic major in use.