Weave Code
Statamic Peak Commands Laravel Package
studio1902/statamic-peak-commands
A set of Artisan commands for Studio 1902's Statamic Peak starter kit that streamlines common setup and scaffolding tasks, helping developers build and maintain Statamic sites faster from the command line.
Belongs to the Statamic Peak Starter Kit and contains all CLI commands and stubs.
Frequently asked questions about Statamic Peak Commands
- What is studio1902/statamic-peak-commands used for?
- It provides Artisan CLI commands and stubs for Studio 1902's Statamic Peak starter kit. The package streamlines common setup and scaffolding tasks so developers can create and maintain Statamic sites faster from the command line. In v11.1.0 it extends the Laravel Artisan make:partial workflow with an optional CSS generation feature.
- How do I install studio1902/statamic-peak-commands?
- Install it with Composer using composer require studio1902/statamic-peak-commands. Because it contains CLI commands and stubs for the Statamic Peak starter kit, teams commonly add it as a development dependency. After installation, confirm the commands are registered in your Artisan command list before using them in scripts or documentation.
- Which Laravel and PHP versions does studio1902/statamic-peak-commands support?
- The package is designed for Laravel applications using the Statamic Peak starter kit, but exact PHP and Laravel constraints are defined in its composer.json. The v11.1.0 release is described as a semver minor, additive developer-experience change, so validate it against your project's Laravel version, PHP version, and Statamic Peak version before upgrading. Check the repository's composer.json and release notes for the authoritative compatibility matrix.
- How does the make:partial CSS generation work and is it opt-in?
- In v11.1.0, the make:partial workflow can optionally create a CSS file and wire in an import for newly generated partials. The technical assessment describes this as opt-in, so existing partials and current behavior should remain unchanged unless teams explicitly adopt the generated CSS path. Verify whether your installed version exposes the behavior through a command option or configuration flag before relying on it in team scaffolding.
- Which frontend bundler or CSS import syntax does the package assume?
- The package is best suited to Laravel teams already using make:partial for Blade or UI component scaffolding with Vite or Mix-based asset pipelines. The exact import syntax and placement depend on the generator's implementation, so review the generated output in a development branch. If your team uses a different asset convention, treat the CSS insertion as opinionated and adjust the generated files or disable the feature.
- Is CSS import insertion idempotent or can it create duplicate imports?
- The assessment flags duplicate imports on repeated generation as a low but real risk. Before rolling the feature out, run the generator more than once with CSS generation enabled and inspect the target import file. If duplicates appear, document the cleanup step or avoid using the CSS option until your workflow guards against repeated insertion.
- Will studio1902/statamic-peak-commands overwrite existing CSS files or cause path collisions?
- File-path collisions and overwritten files are listed as possible failure modes if CSS generation is not guarded. The package is a minor, additive release, but generated files may still conflict with existing component conventions or paths. Test generation in a clean branch and confirm whether the command skips or replaces existing CSS files before using it broadly.
- Can I disable CSS generation or ignore the feature if I do not use generated partials?
- Yes. The CSS generation is described as an opt-in addition to the make:partial workflow, so teams that do not use generated partials or CSS files can ignore it. If your team adopts it but later wants to stop, confirm the command option or configuration flag in your installed version and remove or adjust any generated imports. Existing applications should be able to upgrade without changing current behavior when the feature is not used.
- Is it safe to upgrade to v11.1.0 in an existing Statamic Peak project?
- v11.1.0 is a semver minor release described as additive and low risk, with no migration expected for existing partials. Upgrade in a development branch, run the generator with and without CSS generation, and verify import placement, idempotency, and file paths. Also validate compatibility with your Laravel version, PHP version, frontend bundler, and internal generator conventions before rolling out to feature teams.
- Are the generated outputs tested and documented, and how should teams verify before rollout?
- The assessment calls for checking whether generated outputs are covered by tests and documented, and it recommends verifying behavior in a development branch. Run make:partial with and without CSS generation, inspect the generated CSS and import changes, and repeat generation to check for duplicates. Then update internal scaffolding docs or templates and let CI builds catch path or import issues before wider adoption.
Weaver
How can I help you explore Laravel packages today?