v12.0.4

Changelog

• Uses Image Optimizer module of Next.js 12.0.4 (#86)

v12.0.3

Changelog

• Uses Image Optimizer module of Next.js 12.0.3 (#84)

v12.0.2

Changelog

• Uses Image Optimizer module of Next.js 12.0.2 (#101)
• Use relative path as lambda function local package path (#98)

v12.0.1

In this release we fixed a bug that could occur when using absolute image paths (When you use S3 as backend, you are not affected).
In addition you can now define a new input variable next_image_base_origin that can be used to resolve absolute image paths.

When you set next_image_base_origin = "https://example.com" requests for an absolute image path (/path/to/image.png) are then resolved to the URL https://example.com/path/to/image.png.

We also added a fully featured example how to use next export together with S3 and the image optimizer, check it out: Statically exported Next.js app hosted on S3

Changelog

• Add base origin setting (#94, #95)
• Uses Image Optimizer module of Next.js 12.0.1 (#81)

v12.0.0

This release introduces a new package called Pixel that abstracts the image optimization stuff and makes it usable with platforms other than AWS Lambda.
We plan to offer multiple flavors of it, like express middleware or docker images.

⚠️ Breaking Changes ⚠️

We have removed the output variable cloudfront_origin_image_optimizer that was deprecated since the v11.0.0 release.
To upgrade, please use the output variable cloudfront_origin from now on.

E.g. when using the "With existing CloudFront distribution example" you should make the following changes:

module "next_image_optimizer" {
  source = "milliHQ/next-js-image-optimization/aws"
  ...
}

resource "aws_cloudfront_distribution" "distribution" {
  ...

  dynamic "origin" {
-   for_each = [module.next_image_optimizer.cloudfront_origin_image_optimizer]
+   for_each = [module.next_image_optimizer.cloudfront_origin]
   ...
  }
}

Changelog

• Uses Image Optimizer module of Next.js 12.0.0 (#80)
• Add support for AVIF (#73, #92)
• Fixes "Error while trying to add new domain" bug (#68, #69)
• Remove random strings from resource names (#72, #77)
• Bump sharp from 0.29.1 to 0.29.3 (#79, #85)
• Remove deprecated output cloudfront_origin_image_optimizer (#78, #82)
• Remove referer header from cache key when S3 is used (#87, #91)

v11.1.2

Changelog

• Uses Image Optimizer module of Next.js 11.1.2 (#63)
• Updates sharp to v0.29.1 (#66)
• Bump terraform-aws-lambda module to 2.17.0 (#67)

v11.1.1

The upgrade to Next.js 11.1.1 fixes a potential vulnerability which allowed a XSS-attack.
For more information see the Security Advisory.

Changelog

• Uses Image Optimizer module of Next.js 11.1.1 (#64)

v11.1.0

⚠️ Namespace changed ⚠️

We recently changed the namespace of this module from dealmore to milliHQ.
Make sure to upgrade the source of the module accordingly:

module "next_image_optimizer" {
-  source = "dealmore/next-js-image-optimization/aws"
+  source = "milliHQ/next-js-image-optimization/aws"
}

---

Beginning with this release we change the engine that is used to optimize the images from squoosh to Sharp.
Sharp has a much better performance and is therefore better suited for the job.
Please read the Next.js RFC for more information.

Changelog

• Use sharp as image optimization engine (#51, #57)
• Fix typo for default image sizes (#53, #56)
• Uses Image Optimizer module of Next.js 11.1.0 (#54)

v11.0.1

Maintenance release to keep the module up-to-date with Next.js version.

Changelog

• Uses Image Optimizer module of Next.js 11.0.1 (#49)

v11.0.0

The output cloudfront_origin_image_optimizer is now deprecated.
Use cloudfront_origin instead.

Changelog

• Fixes image optimization for webp format (#44)
  Thanks to @vcnc-hex for contributing!
• Uses Image Optimizer module of Next.js 11.0.0 (#45)
• Add output for cache behavior (#43, #48)
• Bump AWS API Gateway Terraform module from 0.11.0 to 1.1.0 (#47)
• Bump AWS Lambda Terraform module from 1.47.0 to 2.4.0 (#46)