Weave Code
Blade Directives Laravel Package
rapidez/blade-directives
rapidez/blade-directives adds useful Blade directives for Rapidez storefronts, helping Laravel developers keep templates cleaner and more concise by replacing repetitive frontend logic with reusable directives. A small utility package for building Rapidez-based shops.
rapidez/blade-directives adds a set of handy custom Blade directives to Rapidez storefronts, helping you keep templates clean and expressive. Instead of repeating PHP snippets or helper calls, you can use concise directives that slot naturally into Laravel Blade and Rapidez's Vue-powered frontend.
- Drop-in Blade directives for everyday storefront rendering tasks
- Reduces boilerplate and keeps views readable
- Works alongside Rapidez components and Laravel helpers
- Simple Composer installation with no config required
Frequently asked questions about Blade Directives
- What is rapidez/blade-directives and what does it do?
- rapidez/blade-directives is a Composer package that adds practical Blade directives for Rapidez storefronts. It helps you write cleaner, more expressive templates and reduce repetitive markup across product pages, listings, and other frontend views. It is intended for Laravel-based Rapidez projects rather than as a general-purpose Blade replacement.
- How do I install rapidez/blade-directives with Composer?
- Install it with composer require rapidez/blade-directives in your Rapidez project. Then follow the package README for any service provider, configuration, or publish steps. Laravel package auto-discovery may register the provider automatically, but verify the documented setup for your version.
- Which Laravel versions does rapidez/blade-directives support?
- The context provided does not specify exact Laravel version constraints. Check the package composer.json or Packagist listing for supported illuminate/support, PHP, and Rapidez versions before installing. Match those constraints to your application's Laravel version to avoid dependency conflicts.
- Do I need Rapidez to use this Blade directives package?
- It is built for Rapidez storefronts, so it is most useful in a Rapidez project with its frontend views and conventions. Some directives may be generic Blade helpers, but others could rely on Rapidez-specific data or helpers. In a plain Laravel app, confirm each directive works without Rapidez dependencies.
- How do I register or configure the directives in a Laravel app?
- After Composer installation, the package's service provider typically registers the directives with Laravel's Blade compiler. If the README mentions a config file or manual provider registration, follow those steps. You normally do not need to edit Blade compiler code directly.
- Can I use these Blade directives in production Rapidez storefronts?
- Yes, custom Blade directives are compiled into cached PHP views and are suitable for production Rapidez storefronts. Run your normal test suite and clear compiled views during deployment with php artisan view:clear. Also verify that any Rapidez-specific data used by directives is available in production.
- How do I test templates that use Rapidez Blade directives?
- Test views that use the directives with Laravel's view testing helpers, such as rendering the view and asserting the expected HTML. Because directives compile to PHP, also check compiled output when behavior depends on arguments. Clear the view cache between test runs if you change directive implementations.
- Are there performance concerns with custom Blade directives?
- Blade directives compile when views are compiled, so they usually add little runtime overhead after caching. Keep directive logic lightweight and move complex queries or business logic into helpers, view models, or services. Then cache compiled views in production as usual.
- Can I override or extend the provided Blade directives?
- Whether you can override a directive depends on how the package registers it and what the README documents. You can usually define your own Blade::directive with the same name later in bootstrapping, but confirm the package's provider order. Extending or wrapping the package's behavior is safer than assuming overrides are supported.
- What are alternatives to rapidez/blade-directives for cleaner Blade templates?
- Alternatives include Laravel Blade components, custom Blade::directive registrations, view composers, and helper functions. Rapidez's built-in directives and frontend conventions may also cover common cases. Choose components when you need reusable markup with slots, and directives when you need concise compile-time syntax.
Weaver
How can I help you explore Laravel packages today?