Weave Code
Responsive Image Craft Laravel Package
infernalmedia/responsive-image-craft
Responsive Image Craft generates responsive image sets, srcset attributes and picture markup for Laravel apps, with on-the-fly resizing, caching and Blade helpers so every visitor gets a sharp, correctly sized image on any device or screen density, with no manual resizing required.
Responsive Image Craft is a Laravel package that makes serving responsive, optimized images effortless. It generates multiple image sizes, builds correct srcset and sizes attributes, and renders <picture> markup so your layouts stay sharp on every device—without hand-writing image variants.
- Automatic srcset and sizes generation
- Configurable breakpoints and output sizes
- Blade components and directives for clean templates
- On-the-fly resizing with caching
- Support for local and cloud storage disks
Frequently asked questions about Responsive Image Craft
- How do I install infernalmedia/responsive-image-craft in a Laravel app?
- Install it with Composer using composer require infernalmedia/responsive-image-craft, and pin the exact version while the package is still pre-1.0. Publish the package config with the vendor:publish command, then review the breakpoint and image size settings before rendering any markup. A short spike on one low-risk template is the safest way to confirm the API matches your Laravel version.
- Which Laravel and PHP versions does ResponsiveImageCraft support?
- The package is a Laravel-oriented Composer library, but you should check its composer.json and README for the exact supported Laravel and PHP matrix before adoption. Test against your own version matrix rather than assuming broad compatibility, since 0.0.x packages often shift requirements between releases. If derivative generation is involved, also confirm whether GD or Imagick is required.
- How do I configure responsive breakpoints in ResponsiveImageCraft?
- Breakpoints and image size definitions live in a publishable config file, so you can align them with your design system's Tailwind, Bootstrap, or custom breakpoints. Publish the config into the config directory and edit the srcset and sizes entries there instead of hardcoding values in templates. Keeping the breakpoint set small keeps derivative counts, storage use, and cache invalidation manageable.
- Does ResponsiveImageCraft generate image derivatives or only render responsive markup?
- The package's stated focus is responsive image markup with srcset, sizes, and optimized variants, so confirm in the v0.0.10 changelog whether sizes support also creates new derivative files or only changes rendered attributes. If derivatives are generated, expect storage growth and plan queue-based generation plus cache clearing. If it is markup-only, pair it with Intervention Image, Glide, or a CDN that already produces the resized files.
- How do I use the ResponsiveImageCraft Blade component in templates?
- The package ships a flexible display component plus Blade helpers, so you typically pass an image path or media reference to the component and let it output the srcset and sizes attributes. Verify the exact component name and prop names in the README for v0.0.10, since pre-1.0 APIs can change between patch releases. Always include a fallback src attribute so browsers that ignore srcset still load a usable image.
- Can ResponsiveImageCraft work with S3, a CDN, and Laravel filesystem disks?
- Storage behavior depends on how the package resolves image URLs, so check whether it reads from Laravel filesystem disks or assumes local public paths. If disk support exists, point it at your S3 or CDN-backed disk and confirm the generated srcset uses CDN-prefixed URLs. Test cache invalidation end to end, because stale CDN entries for regenerated or renamed derivatives are a common failure mode.
- How do the SCSS mixins for responsive background images work?
- The bundled SCSS mixins let you apply responsive background images without hand-writing a media query for every breakpoint. Import the mixin file into your stylesheet pipeline after your breakpoint variables are defined, then pass the image and size map to the mixin. Confirm the mixin breakpoint names match the PHP config so background images and inline images stay consistent.
- Is ResponsiveImageCraft stable enough for production?
- It is still on 0.0.x, so semver guarantees are limited and breaking changes can arrive in patch or minor releases. Pin the exact version, review changelogs before upgrading, and assign an internal owner for the dependency. A feature-flagged pilot on one non-critical template is a sensible way to evaluate behavior under real traffic before wider rollout.
- How do I test the responsive image markup this package generates?
- Write feature tests that assert the rendered HTML contains the expected srcset, sizes, and fallback src attributes for representative templates. Those assertions catch template regressions and configuration drift after upgrades far better than manual visual checks. If derivatives are generated, also assert the files exist and that a missing image path returns the fallback rather than a 404.
- What happens if responsive image derivatives are missing or generation fails?
- If a derivative is missing or generation fails, the markup can point at a file that does not exist, so add a fallback src and monitor 404s on image paths. Clear caches and regenerate after changing breakpoints or config, since stale entries are a frequent cause of broken images. Also watch for image-driver errors and filesystem permission problems during generation, and consider a graceful degradation path to manual srcset markup.
Weaver
How can I help you explore Laravel packages today?