Weave Code
Blast Laravel Package
area17/blast
Area17 Blast is a Laravel package for rapidly building admin interfaces. It offers reusable Blade and Vue UI components, Tailwind styling, and helpers for forms, tables, and CRUD screens, helping teams ship consistent back-office tools faster.
Storybook for Laravel Blade 🚀
Frequently asked questions about Blast
- How do I install area17/blast in a Laravel application?
- Install it with Composer using composer require area17/blast, then follow the package README to publish any assets or views you want to override. Blast is designed to work alongside standard Laravel conventions and authentication, so no database or queue setup is required. For a fresh adoption, pin the package version and confirm your Laravel version meets the supported constraints.
- Which Laravel versions does area17/blast support?
- Recent Blast releases include Laravel 12.x compatibility, and 11.x is also supported in the current line. Because Laravel majors move quickly, check the package composer constraints before upgrading your application. The 1.11.0 release specifically added Laravel 12.x support through a Laravel Shift compatibility update.
- What can I build with area17/blast?
- Blast provides reusable Blade and Vue UI components plus Tailwind styling for admin interfaces, including forms, tables, filters, navigation, and CRUD screens. It is aimed at back-office tools and internal dashboards where you want consistent markup without rewriting layouts for every screen. Views are publishable, so you can customise the supplied components to match your own design system.
- Do I need Storybook to use area17/blast?
- No. Blast's Blade component library works inside a normal Laravel application without Storybook. The Storybook bridge is a developer-experience and design-system tooling layer that lets teams render and document Blade components in a component workshop. You can adopt the admin UI components first and add Storybook later if your team needs a preview surface.
- How does Blast integrate with Storybook?
- Blast bridges Blade components into Storybook, typically through a Laravel-side rendering endpoint and a CLI or workflow for generating stories from your components. That lets you preview and document Blade views inside Storybook without moving the UI into JavaScript. Treat the Storybook integration as tooling rather than a runtime dependency, and keep the rendering route restricted to local or CI environments.
- Is area17/blast safe to use in production?
- Blast is generally low risk because it sits in the tooling and presentation layer rather than the request/response path. The main concerns are version drift between Laravel and Storybook majors, and ensuring any Storybook rendering endpoint is not exposed publicly in production. The upstream is maintained by Area17 with community PRs, so review latency and bus factor matter if it becomes load-bearing for your design system.
- How do I upgrade area17/blast from 1.10.x to 1.11.0?
- The 1.11.0 release is a drop-in minor bump from 1.10.x with no config changes or breaking API changes signaled. It includes typo fixes, PHP property declaration deprecation cleanup, Laravel 12.x compatibility, and a new option for defining a custom Storybook version. After upgrading, validate your Storybook major explicitly and check CI logs for any remaining deprecation noise.
- How do I set a custom Storybook version in Blast?
- Blast 1.11.0 adds the ability to define the Storybook version your project uses, removing a prior hard coupling between the package's assumed major and your installed major. Set that option explicitly rather than relying on defaults so you control which Storybook major Blast targets. Because the feature is new and likely thinly tested across the version matrix, validate it against the specific Storybook major you run before rolling it out.
- What are alternatives to area17/blast for Laravel admin interfaces?
- Blast is a component library rather than a full admin framework, so teams often compare it with heavier Laravel admin packages or with building their own Blade components. Choose Blast when you want reusable Blade and Vue UI components, Tailwind styling, and optional Storybook previews without adopting an opinionated resource-management framework. If you need complete CRUD generation and authorization out of the box, evaluate broader admin packages instead.
- How should I test area17/blast components in CI?
- Onboard one or two representative Blade components end-to-end before scaling to the full inventory, and render them through Storybook in local or CI environments. Confirm the PHP 8.x deprecation fixes land cleanly on your target PHP version so CI logs stay quiet. Keep generated story files either committed or ephemeral by an explicit policy, and document the Laravel and Storybook versions you test against.
Weaver
How can I help you explore Laravel packages today?