@unpic/[email protected]

Patch Changes

• 01a7062: Fixes a bug that caused unpic props to appear at attributes in the
  img element

@unpic/[email protected]

Patch Changes

• 7fbcc41: chore(deps): expand Next.js peer dependencies to support v16

@unpic/[email protected]

Changelog

1.0.0

Major Changes

• cd0fe95: Welcome to version 1.0.0 of Unpic! 🎉

  This is a major update, with changes to the API of all frameworks. This will
  not affect you if you are just using the components with default options, but
  if you are passing custom transformers or specifying the CDN then you will
  need to update your code.

  Breaking changes

  • The cdnOptions property has been removed. Use the new
    options property instead.
  • The transformer property has been removed from the default Image
    component. Import the base component and specify the
    transformer there instead. The type signature for the transformer has also
    changed. See the unpic library documentation for more information.
  • The cdn property has been removed. Either use the new
    fallback property or import
    the base component and pass a single provider to it.

  Changes

  Most of the changes are because of a new approach to handling individual image
  CDNs and providers in the base Unpic library. This is designed to make Unpic
  more flexible, efficient and modular. It also introduces support for type-safe
  custom operations and options for each provider.

  Provider operations

  Supported frameworks: All except webc and lit.

  The new operations property allows you to specify custom operations for each
  provider. Many image CDNs support dozens of custom operations. Previously
  these were hard to use with Unpic. The new operations property gives
  type-safe support for all supported features of each provider. This works even
  if you have images from multiple providers in the same component, as you can
  specify options for each provider separately.

  <Image
    src="https://example.com/image.jpg"
    operations={{ imgix: { flip: "h" }, bunny: { flop: true } }}
  />

  The operations are all type-safe, with JSDoc comments and TypeScript
  definitions for all supported operations. This means you can get
  autocompletion and type checking for all operations.

  Provider options

  Supported frameworks: All except webc and lit.

  The new options property allows you to specify custom options for each
  provider. This is similar to the current cdnOptions property, but with
  type-safe support for all options of each provider. This allows you to specify
  options such as account IDs and domains for each provider.

  Fallback providers

  Supported frameworks: All. The astro and nextjs frameworks default to the
  framework's image provider as fallback.

  The new fallback property allows you to specify a fallback provider for each
  image. This allows you to use auto-detection for image CDNs as now, but also
  specify a fallback provider for local images and images from unknown
  providers. This is useful if you have a mix of images from different sources,
  and want to ensure that all images are handled correctly. For example, you may
  have a Contentful blog hosted on Netlify, with images that are mostly hosted
  on Contentful (a supported CDN), but also some images from third-parties or
  your own server. You can specify Netlify as the fallback provider so that it
  uses the Netlify Image CDN for all images that are not from Contentful or
  another supported provider. This will be all handled automatically.

  Base component

  Supported frameworks: All except webc, lit and angular.

  Previously, the Image and Source components always loaded support for
  every provider, even if you specified a single provider or custom transformer.
  This is fine if you are using auto-detection, but many people wanted to use
  the components in a more custom or modular way. The new base components allow
  you to use the Unpic component without any of the automatic detection and
  transform logic. You can provide your own transformer, or use a single,
  tree-shakable provider import. This is useful if you are using a single
  provider, or if you are building a custom component based on Unpic.

  // Import from the `/base` subpath
  import { Image } from "@unpic/react/base";
  // Import the transformer for the provider you are using
  import { transform } from "unpic/providers/imgix";
  
  export const Hero = () => (
    <Image
      src="https://images.unsplash.com/photo-1734108039189-f6c123288381"
      transformer={transform}
      operations={{ sepia: 50 }}
    />
  );

  The operations and options properties are still type-safe and inferred
  from the transformer, and you don't need to specify the provider name in the
  operations object.

0.1.0

Minor Changes

• 5080a40: Adds support for passing CDN options

0.0.49 (2024-03-19)

Bug Fixes

• deps: upgrade all dependencies
  (#574)
  (52ca654)

0.0.48 (2024-03-13)

Bug Fixes

• deps: update dependency unpic to ^3.18.0
  (#519)
  (3cd205c)

0.0.47 (2024-02-18)

Bug Fixes

• update (#504)
  (a3775fb)

0.0.46 (2024-02-08)

Bug Fixes

• deps: update dependency unpic to ^3.17.0
  (#493)
  (22b6fd6)

0.0.45 (2024-02-07)

Bug Fixes

• deps: update dependency unpic to ^3.16.1
  (#491)
  (00a4da2)

0.0.44 (2024-01-27)

Features

• astro: add support for placeholders
  (#452)
  (4dbff26)

0.0.43 (2024-01-23)

Features

• astro: add experimental image service
  (#450)
  (552f258)

0.0.42 (2023-12-11)

Bug Fixes

• deps: update dependency unpic to ^3.16.0
  (#413)
  (c41e8cd)

0.0.41 (2023-12-05)

Bug Fixes

• deps: update dependency unpic to ^3.15.0
  (#410)
  (26ad5b2)

0.0.40 (2023-11-16)

Bug Fixes

• deps: update dependency unpic to ^3.14.1
  (#395)
  (9f9db47)

0.0.39 (2023-11-16)

Bug Fixes

• core: add styles to images without transformers
  (#390)
  (d5ae100)

0.0.38 (2023-11-16)

Bug Fixes

• deps: update dependency unpic to ^3.14.0
  (#387)
  (85e542a)

0.0.37 (2023-11-13)

Bug Fixes

• generate correct type declarations for ESM and CJS
  (#371)
  (1738f4e)

0.0.36 (2023-11-07)

Bug Fixes

• deps: update dependency unpic to ^3.13.0
  (#361)
  (eb5ce93)

0.0.35 (2023-11-03)

Features

• svelte: forward load listener on Svelte component
  (86c01c5)

0.0.34 (2023-10-31)

Bug Fixes

• deps: update ...

@unpic/[email protected]

Patch Changes

• 8ea0a80: Updates publishing to ship built files to allow usage with Node type
  stripping, enabled by default in 22.18.0

@unpic/[email protected]

Patch Changes

• e07101d: Fixes a bug that caused images in MDX files to sometimes not display
  when usingtrailingSlash: 'always'.

@unpic/[email protected]

Changelog

1.0.0

Major Changes

• cd0fe95: Welcome to version 1.0.0 of Unpic! 🎉

  This is a major update, with changes to the API of all frameworks. This will
  not affect you if you are just using the components with default options, but
  if you are passing custom transformers or specifying the CDN then you will
  need to update your code.

  Breaking changes

  • The cdnOptions property has been removed. Use the new
    options property instead.
  • The transformer property has been removed from the default Image
    component. Import the base component and specify the
    transformer there instead. The type signature for the transformer has also
    changed. See the unpic library documentation for more information.
  • The cdn property has been removed. Either use the new
    fallback property or import
    the base component and pass a single provider to it.

  Changes

  Most of the changes are because of a new approach to handling individual image
  CDNs and providers in the base Unpic library. This is designed to make Unpic
  more flexible, efficient and modular. It also introduces support for type-safe
  custom operations and options for each provider.

  Provider operations

  Supported frameworks: All except webc and lit.

  The new operations property allows you to specify custom operations for each
  provider. Many image CDNs support dozens of custom operations. Previously
  these were hard to use with Unpic. The new operations property gives
  type-safe support for all supported features of each provider. This works even
  if you have images from multiple providers in the same component, as you can
  specify options for each provider separately.

  <Image
    src="https://example.com/image.jpg"
    operations={{ imgix: { flip: "h" }, bunny: { flop: true } }}
  />

  The operations are all type-safe, with JSDoc comments and TypeScript
  definitions for all supported operations. This means you can get
  autocompletion and type checking for all operations.

  Provider options

  Supported frameworks: All except webc and lit.

  The new options property allows you to specify custom options for each
  provider. This is similar to the current cdnOptions property, but with
  type-safe support for all options of each provider. This allows you to specify
  options such as account IDs and domains for each provider.

  Fallback providers

  Supported frameworks: All. The astro and nextjs frameworks default to the
  framework's image provider as fallback.

  The new fallback property allows you to specify a fallback provider for each
  image. This allows you to use auto-detection for image CDNs as now, but also
  specify a fallback provider for local images and images from unknown
  providers. This is useful if you have a mix of images from different sources,
  and want to ensure that all images are handled correctly. For example, you may
  have a Contentful blog hosted on Netlify, with images that are mostly hosted
  on Contentful (a supported CDN), but also some images from third-parties or
  your own server. You can specify Netlify as the fallback provider so that it
  uses the Netlify Image CDN for all images that are not from Contentful or
  another supported provider. This will be all handled automatically.

  Base component

  Supported frameworks: All except webc, lit and angular.

  Previously, the Image and Source components always loaded support for
  every provider, even if you specified a single provider or custom transformer.
  This is fine if you are using auto-detection, but many people wanted to use
  the components in a more custom or modular way. The new base components allow
  you to use the Unpic component without any of the automatic detection and
  transform logic. You can provide your own transformer, or use a single,
  tree-shakable provider import. This is useful if you are using a single
  provider, or if you are building a custom component based on Unpic.

  // Import from the `/base` subpath
  import { Image } from "@unpic/react/base";
  // Import the transformer for the provider you are using
  import { transform } from "unpic/providers/imgix";
  
  export const Hero = () => (
    <Image
      src="https://images.unsplash.com/photo-1734108039189-f6c123288381"
      transformer={transform}
      operations={{ sepia: 50 }}
    />
  );

  The operations and options properties are still type-safe and inferred
  from the transformer, and you don't need to specify the provider name in the
  operations object.

0.1.0

Minor Changes

• 5080a40: Adds support for passing CDN options

0.0.49 (2024-03-19)

Bug Fixes

• deps: upgrade all dependencies
  (#574)
  (52ca654)

0.0.48 (2024-03-13)

Bug Fixes

• deps: update dependency unpic to ^3.18.0
  (#519)
  (3cd205c)

0.0.47 (2024-02-18)

Bug Fixes

• update (#504)
  (a3775fb)

0.0.46 (2024-02-08)

Bug Fixes

• deps: update dependency unpic to ^3.17.0
  (#493)
  (22b6fd6)

0.0.45 (2024-02-07)

Bug Fixes

• deps: update dependency unpic to ^3.16.1
  (#491)
  (00a4da2)

0.0.44 (2024-01-27)

Features

• astro: add support for placeholders
  (#452)
  (4dbff26)

0.0.43 (2024-01-23)

Features

• astro: add experimental image service
  (#450)
  (552f258)

0.0.42 (2023-12-11)

Bug Fixes

• deps: update dependency unpic to ^3.16.0
  (#413)
  (c41e8cd)

0.0.41 (2023-12-05)

Bug Fixes

• deps: update dependency unpic to ^3.15.0
  (#410)
  (26ad5b2)

0.0.40 (2023-11-16)

Bug Fixes

• deps: update dependency unpic to ^3.14.1
  (#395)
  (9f9db47)

0.0.39 (2023-11-16)

Bug Fixes

• core: add styles to images without transformers
  (#390)
  (d5ae100)

0.0.38 (2023-11-16)

Bug Fixes

• deps: update dependency unpic to ^3.14.0
  (#387)
  (85e542a)

0.0.37 (2023-11-13)

Bug Fixes

• generate correct type declarations for ESM and CJS
  (#371)
  (1738f4e)

0.0.36 (2023-11-07)

Bug Fixes

• deps: update dependency unpic to ^3.13.0
  (#361)
  (eb5ce93)

0.0.35 (2023-11-03)

Features

• svelte: forward load listener on Svelte component
  (86c01c5)

0.0.34 (2023-10-31)

Bug Fixes

• deps: update ...

@unpic/[email protected]

Patch Changes

• f6a53fc: Update React dependencies to support React 19

@unpic/[email protected]

Changelog

1.0.0

Major Changes

• cd0fe95: Welcome to version 1.0.0 of Unpic! 🎉

  This is a major update, with changes to the API of all frameworks. This will
  not affect you if you are just using the components with default options, but
  if you are passing custom transformers or specifying the CDN then you will
  need to update your code.

  Breaking changes

  • The cdnOptions property has been removed. Use the new
    options property instead.
  • The transformer property has been removed from the default Image
    component. Import the base component and specify the
    transformer there instead. The type signature for the transformer has also
    changed. See the unpic library documentation for more information.
  • The cdn property has been removed. Either use the new
    fallback property or import
    the base component and pass a single provider to it.

  Changes

  Most of the changes are because of a new approach to handling individual image
  CDNs and providers in the base Unpic library. This is designed to make Unpic
  more flexible, efficient and modular. It also introduces support for type-safe
  custom operations and options for each provider.

  Provider operations

  Supported frameworks: All except webc and lit.

  The new operations property allows you to specify custom operations for each
  provider. Many image CDNs support dozens of custom operations. Previously
  these were hard to use with Unpic. The new operations property gives
  type-safe support for all supported features of each provider. This works even
  if you have images from multiple providers in the same component, as you can
  specify options for each provider separately.

  <Image
    src="https://example.com/image.jpg"
    operations={{ imgix: { flip: "h" }, bunny: { flop: true } }}
  />

  The operations are all type-safe, with JSDoc comments and TypeScript
  definitions for all supported operations. This means you can get
  autocompletion and type checking for all operations.

  Provider options

  Supported frameworks: All except webc and lit.

  The new options property allows you to specify custom options for each
  provider. This is similar to the current cdnOptions property, but with
  type-safe support for all options of each provider. This allows you to specify
  options such as account IDs and domains for each provider.

  Fallback providers

  Supported frameworks: All. The astro and nextjs frameworks default to the
  framework's image provider as fallback.

  The new fallback property allows you to specify a fallback provider for each
  image. This allows you to use auto-detection for image CDNs as now, but also
  specify a fallback provider for local images and images from unknown
  providers. This is useful if you have a mix of images from different sources,
  and want to ensure that all images are handled correctly. For example, you may
  have a Contentful blog hosted on Netlify, with images that are mostly hosted
  on Contentful (a supported CDN), but also some images from third-parties or
  your own server. You can specify Netlify as the fallback provider so that it
  uses the Netlify Image CDN for all images that are not from Contentful or
  another supported provider. This will be all handled automatically.

  Base component

  Supported frameworks: All except webc, lit and angular.

  Previously, the Image and Source components always loaded support for
  every provider, even if you specified a single provider or custom transformer.
  This is fine if you are using auto-detection, but many people wanted to use
  the components in a more custom or modular way. The new base components allow
  you to use the Unpic component without any of the automatic detection and
  transform logic. You can provide your own transformer, or use a single,
  tree-shakable provider import. This is useful if you are using a single
  provider, or if you are building a custom component based on Unpic.

  // Import from the `/base` subpath
  import { Image } from "@unpic/react/base";
  // Import the transformer for the provider you are using
  import { transform } from "unpic/providers/imgix";
  
  export const Hero = () => (
    <Image
      src="https://images.unsplash.com/photo-1734108039189-f6c123288381"
      transformer={transform}
      operations={{ sepia: 50 }}
    />
  );

  The operations and options properties are still type-safe and inferred
  from the transformer, and you don't need to specify the provider name in the
  operations object.

0.1.0

Minor Changes

• 5080a40: Adds support for passing CDN options

0.0.49 (2024-03-19)

Bug Fixes

• deps: upgrade all dependencies
  (#574)
  (52ca654)

0.0.48 (2024-03-13)

Bug Fixes

• deps: update dependency unpic to ^3.18.0
  (#519)
  (3cd205c)

0.0.47 (2024-02-18)

Bug Fixes

• update (#504)
  (a3775fb)

0.0.46 (2024-02-08)

Bug Fixes

• deps: update dependency unpic to ^3.17.0
  (#493)
  (22b6fd6)

0.0.45 (2024-02-07)

Bug Fixes

• deps: update dependency unpic to ^3.16.1
  (#491)
  (00a4da2)

0.0.44 (2024-01-27)

Features

• astro: add support for placeholders
  (#452)
  (4dbff26)

0.0.43 (2024-01-23)

Features

• astro: add experimental image service
  (#450)
  (552f258)

0.0.42 (2023-12-11)

Bug Fixes

• deps: update dependency unpic to ^3.16.0
  (#413)
  (c41e8cd)

0.0.41 (2023-12-05)

Bug Fixes

• deps: update dependency unpic to ^3.15.0
  (#410)
  (26ad5b2)

0.0.40 (2023-11-16)

Bug Fixes

• deps: update dependency unpic to ^3.14.1
  (#395)
  (9f9db47)

0.0.39 (2023-11-16)

Bug Fixes

• core: add styles to images without transformers
  (#390)
  (d5ae100)

0.0.38 (2023-11-16)

Bug Fixes

• deps: update dependency unpic to ^3.14.0
  (#387)
  (85e542a)

0.0.37 (2023-11-13)

Bug Fixes

• generate correct type declarations for ESM and CJS
  (#371)
  (1738f4e)

0.0.36 (2023-11-07)

Bug Fixes

• deps: update dependency unpic to ^3.13.0
  (#361)
  (eb5ce93)

0.0.35 (2023-11-03)

Features

• svelte: forward load listener on Svelte component
  (86c01c5)

0.0.34 (2023-10-31)

Bug Fixes

• deps: update ...

@unpic/[email protected]

Major Changes

• cd0fe95: Welcome to version 1.0.0 of Unpic! 🎉

  This is a major update, with changes to the API of all frameworks. This will
  not affect you if you are just using the components with default options, but
  if you are passing custom transformers or specifying the CDN then you will
  need to update your code.

  Breaking changes

  • The cdnOptions property has been removed. Use the new
    options property instead.
  • The transformer property has been removed from the default Image
    component. Import the base component and specify the
    transformer there instead. The type signature for the transformer has also
    changed. See the unpic library documentation for more information.
  • The cdn property has been removed. Either use the new
    fallback property or import
    the base component and pass a single provider to it.

  Changes

  Most of the changes are because of a new approach to handling individual image
  CDNs and providers in the base Unpic library. This is designed to make Unpic
  more flexible, efficient and modular. It also introduces support for type-safe
  custom operations and options for each provider.

  Provider operations

  Supported frameworks: All except webc and lit.

  The new operations property allows you to specify custom operations for each
  provider. Many image CDNs support dozens of custom operations. Previously
  these were hard to use with Unpic. The new operations property gives
  type-safe support for all supported features of each provider. This works even
  if you have images from multiple providers in the same component, as you can
  specify options for each provider separately.

  <Image
    src="https://example.com/image.jpg"
    operations={{ imgix: { flip: "h" }, bunny: { flop: true } }}
  />

  The operations are all type-safe, with JSDoc comments and TypeScript
  definitions for all supported operations. This means you can get
  autocompletion and type checking for all operations.

  Provider options

  Supported frameworks: All except webc and lit.

  The new options property allows you to specify custom options for each
  provider. This is similar to the current cdnOptions property, but with
  type-safe support for all options of each provider. This allows you to specify
  options such as account IDs and domains for each provider.

  Fallback providers

  Supported frameworks: All. The astro and nextjs frameworks default to the
  framework's image provider as fallback.

  The new fallback property allows you to specify a fallback provider for each
  image. This allows you to use auto-detection for image CDNs as now, but also
  specify a fallback provider for local images and images from unknown
  providers. This is useful if you have a mix of images from different sources,
  and want to ensure that all images are handled correctly. For example, you may
  have a Contentful blog hosted on Netlify, with images that are mostly hosted
  on Contentful (a supported CDN), but also some images from third-parties or
  your own server. You can specify Netlify as the fallback provider so that it
  uses the Netlify Image CDN for all images that are not from Contentful or
  another supported provider. This will be all handled automatically.

  Base component

  Supported frameworks: All except webc, lit and angular.

  Previously, the Image and Source components always loaded support for
  every provider, even if you specified a single provider or custom transformer.
  This is fine if you are using auto-detection, but many people wanted to use
  the components in a more custom or modular way. The new base components allow
  you to use the Unpic component without any of the automatic detection and
  transform logic. You can provide your own transformer, or use a single,
  tree-shakable provider import. This is useful if you are using a single
  provider, or if you are building a custom component based on Unpic.

  // Import from the `/base` subpath
  import { Image } from "@unpic/react/base";
  // Import the transformer for the provider you are using
  import { transform } from "unpic/providers/imgix";
  
  export const Hero = () => (
    <Image
      src="https://images.unsplash.com/photo-1734108039189-f6c123288381"
      transformer={transform}
      operations={{ sepia: 50 }}
    />
  );

  The operations and options properties are still type-safe and inferred
  from the transformer, and you don't need to specify the provider name in the
  operations object.

Patch Changes

• Updated dependencies [cd0fe95]
  • @unpic/[email protected]

@unpic/[email protected]

Patch Changes

• 2139c6b: Adds default export