- How do I install laravel-glider in a Laravel application?
- Install it with Composer using daikazu/laravel-glider. The package supports Laravel package auto-discovery, so the service provider is registered automatically. Publish the config and Blade views if you need to customize defaults, then use the Glider Blade components in your templates.
- What is the difference between x-glider-bg and x-glider-bg-responsive?
- Both are Blade components for rendering Glide-powered backgrounds, but only x-glider-bg-responsive supports the preset and breakpoints props. The x-glider-bg component does not support those props, and older README examples that applied them there produced non-functional markup. Use x-glider-bg-responsive whenever you need preset or breakpoint-driven behavior.
- Does laravel-glider support presets and breakpoints for responsive images?
- Yes, but only through the x-glider-bg-responsive component. Presets and breakpoints are not supported on the standard x-glider-bg component. If you copied examples from an older README, search your codebase for x-glider-bg usages that pass preset or breakpoints and move them to the responsive component.
- Which Laravel and PHP versions does laravel-glider v4.1.0 support?
- The release notes do not state a Laravel or PHP support matrix or CI coverage. Check the package composer.json constraints and the repository CI configuration before adopting it in a version-sensitive project. If your application runs an older Laravel line, confirm compatibility rather than assuming it.
- Is laravel-glider an admin panel or CRUD package?
- No. Some package descriptions describe it as an admin panel and CRUD builder, but the actual package is a Blade component package for on-the-fly Glide image rendering. It provides components such as x-glider-bg and x-glider-bg-responsive along with publishable configuration and views. Evaluate it as a presentation-layer image tool, not as a CRUD generator.
- What does Laravel Boost support add to laravel-glider?
- Laravel Boost support is opt-in developer tooling introduced in v4.1.0. Running the Boost installer adds a guideline and a glider-development skill to the host application so AI-assisted coding follows the correct component conventions. It is intended for development environments and does not change how the package renders images in production.
- Do I need Vite or a front-end build to use laravel-glider?
- The package sits at the Blade presentation layer, but the release notes do not document its asset pipeline expectations. Confirm whether it ships compiled assets or expects your Vite or npm build to provide styling, and check whether image processing or CDN delivery is your responsibility. Verify this before rolling out to avoid missing styles in production.
- Is upgrading laravel-glider from v3 to v4 a breaking change?
- Treat v3 to v4 as a major upgrade because the v4 line may contain breaking changes that are not detailed in the v4.1.0 notes. Audit every component usage, review the changelog, and regression-test responsive rendering across breakpoints. Upgrading from 4.0.x to 4.1.0 is additive and requires no application code changes.
- How do I fix Glider markup copied from an older README?
- Search your templates for x-glider-bg usages that pass preset or breakpoints props. Move those usages to x-glider-bg-responsive, which is the component that actually supports them. Then visually check the rendered output at your target viewports, since the old markup may have been silently misconfigured.
- Is laravel-glider safe for production and how should I maintain it?
- Risk is low for the v4.1.0 release because it is semver-minor with no declared breaking changes or dependency changes. Pin the minor version, enable automated dependency pull requests, and read the changelog on each release because component documentation has already caused user error once. Keep the Boost guideline regenerated when component props change, and focus scaling effort on image weight and CDN delivery rather than Blade rendering.