v1.8.0

• Updates dependencies; in particular SVGR v8.0.1 ⇒ v8.1.0 (SVGR release notes).
• Drops support for Node v14 & v19 (removed from test environments in CI/CD flow, as both have reached their end-of-life); adds support for Node v20 (added to the test environments in CI/CD flow, this is the new current Node version). See also Node release schedule.

v1.7.0

• Updates dependencies; in particular SVGR v7.0.0 ⇒ v8.0.1 (SVGR release notes).

v1.6.0

• Updates dependencies; in particular:
  • SVGR v6.5.1 ⇒ v7.0.0 (SVGR release notes);
  • SVGO v2.8.0 ⇒ v3.0.2 (SVGO release notes).

v1.5.1

• Updates dependencies.

v1.5.0

• Updates dependencies, in particular SVGR v6.3.0 ⇒ 6.5.0 (see SVGR Changelog).
• It is marked as a minor version update because new SVGR version adds role="img" attribute to generated <svg> elements.
• Also since this release the compatibility with Node 12 (which reached its end-of-life on April 30, 2022) is not guaranteed. This is because the latest versions of packages (ESLint, Jest) used for testing of this preset in CI/CD do not work on Node 12, thus CI/CD is performed now in the environment with Node 14.20.1 (it is currently in maintenance status, with its end-of-life planned on Apr 30, 2023).

v1.4.2

• Updates dependencies.

v1.4.1

Update of dependencies.

v1.4.0

Breaking Changes

• Migration to SVGR v6 (v5.5.0 → v6.0.0). Under the hood it means SVGO migration v1.3.2 → v2.8.0, and alters output SVG code for the same SVG input, compared to the previous version. If you rely on custom SVGO configuration, this update changes how it should be configured. You may check other changes caused by SVGO upgrade in their release notes.

v1.3.1

• [#16] Small README correction: the Babel's flag to keep file extensions is --keep-file-extension (it was written with trailing s before).
  ⇒ Thanks to @saveman71
• Updates of dev dependencies ⇒ irrelevant to end users.

v1.3.0

• Updated to use SVGR v5.5.0. Marked as a minor version update because SVGR now keeps xmlns attributes in the processed SVGs. It may require to update your snapshot tests accordingly, etc.