Weave Code
Image Resizer Laravel Package
rapidez/image-resizer
On-the-fly image resizing for Rapidez storefronts. Generate optimized, cached product image variants at any dimension directly from templates, keeping Magento media URLs intact and your pages fast. Simple Blade helpers let you request exactly the size you need without storing duplicates.
At a glance
Frequently asked questions about Image Resizer
- How do I install rapidez/image-resizer in my Rapidez project?
- Install it with Composer using composer require rapidez/image-resizer in your Rapidez storefront. Then follow the README for any required configuration or publishing steps. Because Rapidez runs on Laravel, the normal Composer and Laravel package workflows apply.
- Will it break my existing Magento media URLs?
- No. The package is designed to keep Magento media URLs intact while generating resized variants on the fly. Your templates request a specific size, and the package serves the generated variant without changing the underlying Magento media path. That means existing media handling and integrations can keep working as before.
- How do I request a specific image size in a Blade template?
- Use the provided Blade helpers and pass the image URL plus the dimensions you need, such as a width and height for the target slot. The helper returns the URL for the generated, cached variant so you can drop it straight into an img tag. The goal is to request exactly the size the layout needs rather than loading a large original and scaling it with CSS.
- Are the resized images cached, and where are they stored?
- Yes, generated variants are cached so repeated requests do not re-run the resize. The cache location should be a persistent, writable directory in your Laravel storage and is typically configurable in the package settings. In production, make sure that directory is shared across app servers or served through a CDN.
- Does it create duplicate image files for every possible size?
- It only creates variants for the dimensions your templates actually request, and those variants are cached. It does not pre-generate or store duplicates for every possible size. If you change the dimensions used in templates, new variants are generated and the old ones can be cleaned up.
- Which Laravel and Rapidez versions does this package support?
- The package is built for Rapidez storefronts, which run on Laravel, so your Laravel version needs to match what your Rapidez release supports. Check the composer.json constraints in the package repository for the exact PHP, Laravel, and Rapidez version requirements. If you are on an older Rapidez release, verify compatibility before adding it to production.
- How do I clear cached images after changing dimensions?
- Delete the cached variant files from the configured cache directory, or use Laravel's storage and cache commands if the package stores metadata there. After clearing, the next request for a given size will regenerate the image. It is a good idea to warm the cache for your most important product pages after a change.
- Can I use it outside Blade templates, for example in a controller or API response?
- The documented interface is Blade helpers for template use, which covers most Rapidez storefront needs. For controllers or API responses, you can call the same underlying resizing logic if the package exposes it, or generate the URL through the equivalent service. Check the README for the supported API before relying on it outside Blade.
- What is the performance impact in production?
- The first request for a new size generates and caches the variant, so there is a one-time resize cost. After that, requests serve the cached file, which keeps pages fast. For high-traffic stores, warm the cache after deploys and serve the cached directory through a CDN or reverse proxy.
- What are the alternatives to rapidez/image-resizer?
- Alternatives include Magento's native image resizing and cache, generic Laravel image packages such as intervention/image combined with a caching layer, or a CDN with on-the-fly image transformation. The advantage here is that it is purpose-built for Rapidez storefronts and keeps Magento media URLs intact. Evaluate based on whether you need storefront Blade helpers or a broader image pipeline.
Weaver
How can I help you explore Laravel packages today?