Weave Code
Statamic Peak Tools Laravel Package
studio1902/statamic-peak-tools
Handy utilities for Statamic from Studio 1902, built to complement the Peak starter kit. Adds practical tags, modifiers and helpers that speed up everyday site building, so you spend less time on boilerplate and more on content and design.
Belongs to the Statamic Peak Starter Kit and contains shared Antlers tools.
Frequently asked questions about Statamic Peak Tools
- What is studio1902/statamic-peak-tools used for?
- It is a companion Composer package to the Statamic Peak starter kit, providing shared Antlers tags, modifiers, partials and helpers used by Peak templates. It is not a general-purpose Laravel library; its scope is the Antlers rendering layer inside a Statamic site. It speeds up Peak-based site building by reducing everyday template boilerplate.
- Does studio1902/statamic-peak-tools work without the Statamic Peak starter kit?
- Not reliably. The tools are described as shared within Peak and likely assume Peak's blueprint and fieldset naming conventions. Without Peak there is no compelling standalone use case for a package this small. You could vendor and adapt individual partials, but that is effectively a fork-style approach.
- How do I install studio1902/statamic-peak-tools in a Laravel Statamic app?
- Mechanically it is a composer require plus Statamic addon service provider autoloading. However, if you are using Peak you normally receive it as a transitive dependency and should pin Peak rather than this package directly. Confirm the statamic/cms and laravel/framework constraints against your pinned versions before committing.
- Which Laravel, PHP and Statamic versions does statamic-peak-tools support?
- The package targets the Laravel plus Statamic plus Antlers stack; the evaluation's target shape is Laravel 10/11, Statamic 4/5 and PHP 8.1+. Exact statamic/cms and laravel/framework constraints must be checked on Packagist against your pinned versions before committing. Also verify release metadata directly, since the listed future release date looks like registry noise.
- Is studio1902/statamic-peak-tools GPL-3.0 and is that a problem for client projects?
- The evaluation flags GPL-3.0 as copyleft and viral. For an internal or agency-owned site that is never distributed it is generally tolerable, but for client deliverables, resale or packaged products legal review is warranted. Treat derivative template work as the area that needs review before adoption.
- Can I use the Antlers tags and modifiers in a non-Peak Statamic site?
- It is built as shared Antlers tools for Peak, so partials likely assume Peak blueprint and fieldset conventions. They will not necessarily drop into an arbitrary Statamic site unmodified. If you only want a few utilities, vendor selected partials and adapt them explicitly.
- Is statamic-peak-tools actively maintained, and what is the bus factor?
- Community footprint is negligible and it is effectively a single-studio project with no independent maintainer bench or documented security response process. There is no evidence of external contribution. Treat it as a Peak internal detail and plan a fallback for the partials you actually use.
- Should I require statamic-peak-tools directly or let it come via statamic-peak?
- If you adopt Peak, prefer pinning studio1902/statamic-peak and let statamic-peak-tools arrive transitively. Requiring it directly couples composer.json to an internal Peak detail and complicates upgrades. Only require it directly if you are deliberately vendoring selected tools outside Peak.
- Does statamic-peak-tools work with Statamic Blade or the Element API instead of Antlers?
- The package's value proposition is Antlers tooling, so it does not help if you are moving to Statamic Blade views or the Element API. Statamic has been de-emphasizing Antlers, which is directional risk for this package. On a Blade or Livewire-first codebase it adds a second templating idiom for marginal benefit.
- What are alternatives to statamic-peak-tools if I do not adopt Peak?
- There is no compelling standalone alternative for these exact Peak partials; the real alternative is not adopting Peak or reimplementing the few utilities you need. For general Statamic addon needs, evaluate maintained packages with clear support policies. If you need Blade-first tooling, follow Statamic's Blade and Element API direction rather than Antlers helpers.
Weaver
How can I help you explore Laravel packages today?