Release v3.0.1

Fixed

• The maxDensity field in metadata files when -max-density 1 is specified now gets the correct value instead of the erroneous null.

Release v3.0.0

Changed

• Full option names are now spelled out in the kebab-case.
• The --target-format option now accepts a single value, but you can specify the option multiple times to pass multiple values. For example, the equivalent of the default: -f avif -f webp.
• In files generated by the --add-meta-data option, the sizes array is now sorted from smaller breakpoint to larger. The size without a breakpoint is still placed at the end of the array.

Release v2.1.3

Fixed

• The progressbar now fills correctly with the -a flag.

Release v2.1.2

Fixed

• Output directory and file names are now correctly generated when ./ is specified in the -i flag.
• Progressbar no longer erases error messages.

Release v2.1.1

Fixed

• The images command with the -r flag now removes the source file only if no errors occurred during its processing.
• Error messages for the images command are now more readable.
• The verbose and useless images command execution messages have been replaced by a compact and clear progressbar.
• Source file extensions can now be in uppercase.

Release v2.1.0

Added

• The --addMetaData (-m) flag is now also available for the icons command. Enabling it will create an index.css file in the output directory, which contains registrations of custom properties with paths to icons.
• The --originDensity (-d) option now takes the value 0. This works like the 1 value, but without adding the density suffix to the filename.

Release v2.0.0

Changed

• The favicons command no longer depends on the following options:
  • -i — the path to the directory with the files to be processed is now specified with the -p option;
  • -o — new files are created in the same directory as the original files (i.e., the directory specified by the -p option);
  • -r — the original favicon files are now always deleted after processing is complete.
• The favicons command now places only the favicon.ico, manifest.webmanifest, and Links.md files in the specified directory, with all other files being placed in the favicons subdirectory. This eliminates the need to manually move the listed files up one level. You only need to extract the link tags code from the Links.md file into your HTML layout and then delete the Links.md file.

Added

• New CLI option -p (--publicDirectory) for the favicons command, allowing you to specify a directory (public by default) with static assets where the source SVG files for generating favicons are expected.
• New CLI flag -m (--addMetaData), enabling which when processing raster images additionally generates metadata files in JSON and JS formats.

Release v1.0.3

Fixed

• The path to icon-180.png (Apple touch icon) is now correctly generated in Links.md.

Release v1.0.2

Fixed

• Paths in the webmanifest are now generated correctly on Windows.

Release v1.0.1

Fixed

• The conjure favicons command now works fine on Windows.
• The webmanifest is now generated with a final newline.