Skip to content

Releases: simonihmig/responsive-image

@responsive-image/[email protected]

17 Nov 14:18
73eb0e5
Compare
Choose a tag to compare
Pre-release

Patch Changes

@responsive-image/[email protected]

28 Sep 17:51
774d779
Compare
Choose a tag to compare
Pre-release

Minor Changes

  • #663 3ab97bd Thanks @simonihmig! - Do not apply default value for quality

    Instead we rely on sharp's own defaults. For .avif images this will use a lower quality setting (50 instead of 80), which produces smaller sizes with almost the same visual quality as e.g. 80 for jpegs.

  • #669 e2d6111 Thanks @simonihmig! - Add caching support

    Generated images will be cached, based on the source and image processing config. This is especially useul for the vite-plugin in dev mode (serve), since images are processed on-demand within the Vite dev server middleware.

  • #664 bab7cae Thanks @simonihmig! - Rename all eri-* attributes and classes to ri-* for consistency

Patch Changes

@responsive-image/[email protected]

28 Sep 17:51
774d779
Compare
Choose a tag to compare
Pre-release

Minor Changes

  • #663 3ab97bd Thanks @simonihmig! - Do not apply default value for quality

    Instead we rely on sharp's own defaults. For .avif images this will use a lower quality setting (50 instead of 80), which produces smaller sizes with almost the same visual quality as e.g. 80 for jpegs.

  • #669 e2d6111 Thanks @simonihmig! - Add caching support

    Generated images will be cached, based on the source and image processing config. This is especially useul for the vite-plugin in dev mode (serve), since images are processed on-demand within the Vite dev server middleware.

  • #664 bab7cae Thanks @simonihmig! - Rename all eri-* attributes and classes to ri-* for consistency

Patch Changes

@responsive-image/[email protected]

28 Sep 17:51
774d779
Compare
Choose a tag to compare
Pre-release

Minor Changes

@responsive-image/[email protected]

28 Sep 17:51
774d779
Compare
Choose a tag to compare
Pre-release

Minor Changes

  • #663 3ab97bd Thanks @simonihmig! - Do not apply default value for quality

    Instead we rely on sharp's own defaults. For .avif images this will use a lower quality setting (50 instead of 80), which produces smaller sizes with almost the same visual quality as e.g. 80 for jpegs.

  • #669 e2d6111 Thanks @simonihmig! - Add caching support

    Generated images will be cached, based on the source and image processing config. This is especially useul for the vite-plugin in dev mode (serve), since images are processed on-demand within the Vite dev server middleware.

  • #664 bab7cae Thanks @simonihmig! - Rename all eri-* attributes and classes to ri-* for consistency

Patch Changes

  • #660 1c903cd Thanks @simonihmig! - Refactor build plugins, extract shared functionality into @response-image/build-utils

@responsive-image/[email protected]

12 Sep 22:48
f8f99e0
Compare
Choose a tag to compare
Pre-release

Major Changes

  • #608 a3f94f2 Thanks @simonihmig! - Use imagetools for more image processing options

    @responsive-image/webpack is now using the imagetools-core package for image processing via sharp. This now supports not only scaling to different sizes and generating different image formats as before, but also a lot of other directives for image manipulation.

    Breaking Changes: Some parameters passed to the loader as defaults directly or using as query parameters in imports had to change to align with that library:

    • widths has been renamed to w
    • formats to format
    • the separator for array vlues has been changed to ; instead of ,

    Example: import image from './path/to/image.jpg?w=400;800&responsive';

@responsive-image/[email protected]

12 Sep 22:48
f8f99e0
Compare
Choose a tag to compare
Pre-release

Minor Changes

@responsive-image/[email protected]

12 Sep 22:48
f8f99e0
Compare
Choose a tag to compare
Pre-release

Major Changes

  • #614 2d10626 Thanks @simonihmig! - Use Record-based API for cloudinary transformations

    Instead of passing cloudinary transformations as a string according to the Cloudinary Transformation URL API, you need to pass them as an object. If you want to use chained transformations, pass an array of objects.

    // using @resposive-image/cdn
    const simpleTransformation = cloudinaryProvider('foo/bar.jpg', {
      transformations: { co: 'rgb:20a020', e: 'colorize:50' },
    });
    
    const chainedTransformation = cloudinaryProvider('foo/bar.jpg', {
      transformations: [
        { co: 'rgb:20a020', e: 'colorize:50' },
        { ar: '1.0', c: 'fill', w: '150' },
        { r: 'max' },
      ],
    });
    {{!-- using @responsive-image/ember }}
    <ResponsiveImage
      @src={{responsiveImageCloudinaryProvider
        "foo/bar.jpg"
        transformations=(hash co="rgb:20a020" e="colorize:50")
      }}
    >

Patch Changes

@responsive-image/[email protected]

12 Sep 22:47
f8f99e0
Compare
Choose a tag to compare
Pre-release

Major Changes

  • #614 2d10626 Thanks @simonihmig! - Use Record-based API for cloudinary transformations

    Instead of passing cloudinary transformations as a string according to the Cloudinary Transformation URL API, you need to pass them as an object. If you want to use chained transformations, pass an array of objects.

    // using @resposive-image/cdn
    const simpleTransformation = cloudinaryProvider('foo/bar.jpg', {
      transformations: { co: 'rgb:20a020', e: 'colorize:50' },
    });
    
    const chainedTransformation = cloudinaryProvider('foo/bar.jpg', {
      transformations: [
        { co: 'rgb:20a020', e: 'colorize:50' },
        { ar: '1.0', c: 'fill', w: '150' },
        { r: 'max' },
      ],
    });
    {{!-- using @responsive-image/ember }}
    <ResponsiveImage
      @src={{responsiveImageCloudinaryProvider
        "foo/bar.jpg"
        transformations=(hash co="rgb:20a020" e="colorize:50")
      }}
    >

@responsive-image/[email protected]

01 Jun 16:44
ad6be4e
Compare
Choose a tag to compare
Pre-release

Patch Changes