# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/). ## [2.4.0] - 2026-07-22 ### Added - Optional native `webpOptions` and `avifOptions`, passed unchanged to Sharp's `.webp()` and `.avif()` methods. Omitting them preserves Sharp defaults and existing generated targets continue to be skipped. - Optional `outputNaming: "preserve"` strategy, which keeps the source extension in generated names (`logo.png.webp`) so same-basename sources cannot overwrite each other's derivatives. The default remains `"replace"` for backward compatibility. - A single `npm run verify` release gate covering syntax, focused and regression tests, production dependency audit, and the npm package allowlist. `prepublishOnly` now runs this gate automatically. - Replaced opaque atomic-write temp names with self-describing plugin-owned `.incomplete` names, while keeping target-local staging and atomic rename publication. - Added conservative startup cleanup for exact plugin-owned `.incomplete` files older than 24 hours; foreign, fresh, excluded, and symlinked entries are preserved. - Corrected the forced-interruption regression to accept the unavoidable diagnostic artifact after `SIGKILL` and validate any published image by decoding it with Sharp. ### Fixed - Deduplicated source paths from duplicate or overlapping watched folders during the initial pass. - Added collision warnings in the default `"replace"` naming mode when distinct sources resolve to the same WebP or AVIF target. - Made `server.close()` wait for registered initial-pass and live conversion work before completing shutdown, while preserving per-server watcher cleanup for middleware-mode and Nuxt restarts. - Corrected per-file success logs so existing targets counted as `skipped` are no longer reported as successful conversions. - Replaced a timing-dependent race-test log-order assertion with observable output invariants and made the Windows format-options fixture cleanup fail visibly. ### Security - Raised the Sharp dependency floor to `^0.35.0`, excluding versions affected by the inherited libvips vulnerabilities reported by `GHSA-f88m-g3jw-g9cj`. ## [2.3.1] - 2026-07-05 ### Changed - Dev logging now goes through Vite's `logger` (`info`/`warn`/`warnOnce`/`error`) instead of raw `console.*`, so plugin output respects Vite's `logLevel` and `clearScreen` settings. - Unified the log prefix to `[vite-webp-avif-generator]` (matching the plugin `name`), replacing the previous `[Image Converter]` label. Update any log parsing that matched the old prefix. ## [2.3.0] - 2026-07-04 ### Added - New `publicDir` option to explicitly override the public directory used to resolve `public/...`-style `folders`/`exclude` entries. This is required for reliable Nuxt support: Nuxt always sets Vite's own `publicDir` to `false` (on both the client and SSR dev servers, regardless of `srcDir`), so it could never be auto-detected there, and relative `public/...` paths could silently resolve to a non-existent folder under `srcDir` instead of the project's real `public/` directory. - Startup logging now prints each configured folder next to its resolved absolute path, and a one-time warning is logged for any resolved watch folder that doesn't exist on disk, pointing at the new `publicDir` option as a possible fix. - `playground/scripts/test-nuxt-srcdir-public.mjs` reproduces the exact Nuxt condition (`root` shifted + `publicDir: false`) that previously caused a silent `processed 0`, and verifies the `publicDir` option fixes it without changing standard Vite behavior. ### Changed - Corrected the README's Nuxt Support guidance, which previously implied `public/...` paths resolve automatically in Nuxt; this was never reliable once `srcDir` differs from the project root, because Nuxt unconditionally disables Vite's own `publicDir` detection. - Console output for watched/excluded folders gained extra `configured -> resolved` lines; the original single-line summaries are unchanged, so existing log parsing continues to match, but any strict line-count assertions should account for the new lines. - Widened the `chokidar` peer range to include `^5.0.0` and the `sharp` range to include `^0.35.0`. Verified against the full `playground/scripts/run-tests.mjs` suite (42/42) with `chokidar@5.0.0` and `sharp@0.35.3` actually installed. This is a backward-compatible, additive change: the `publicDir` option defaults to unset, in which case path resolution and default behavior are unchanged from `2.2.3`. ## [2.2.3] - 2026-07-04 ### Added - One-time idempotent initial conversion pass for images already present in watched folders on dev server start, controlled by the new `enableInitialPass` option (default `true`). - Recursive, symlink-safe file listing for the initial pass, with an internal concurrency limit for conversions. ### Changed - Converted images are now written atomically (temp file + rename), preventing partial target files if the process is interrupted mid-write. Applies to both live and initial-pass conversions. - The initial conversion pass now waits for the file watcher's `ready` event before starting, narrowing the window in which files added right after server start could be missed by both the live watcher and the initial pass. ### Fixed - Closed the file watcher by wrapping each dev server instance's own `close()` method instead of `server.httpServer.once("close", ...)`, fixing a leak in Vite middleware-mode setups (such as Nuxt) where `server.httpServer` is `null` and the previous cleanup never ran. This supersedes the `[2.2.1]` fix below, which only addressed the standard (non-middleware) case. - Fixed a watcher leak affecting real Nuxt projects: Nuxt runs two independent Vite dev servers (client build and server/SSR build) from the same `convertImages()` plugin instance passed via `nuxt.config.ts`. Cleanup state (the watcher and its idempotency flag) is now local to each `configureServer(server)` call instead of shared across the plugin instance, so closing one server's watcher can no longer overwrite or leak the other's — verified against real `nuxi dev` runs on Nuxt 3.21.8 and 4.4.8, including config-triggered restarts. This also removes a narrower, previously-documented edge case with Vite's own `server.restart()` reusing inline plugin instances. - Errors thrown by `watcher.close()` are now caught and logged instead of propagating, so a failed close no longer blocks the rest of the dev server shutdown sequence. ## [2.2.1] - 2026-04-02 ### Fixed - Kept the image watcher alive for the whole Vite dev server lifecycle by closing it on the HTTP server `close` event instead of using the `configureServer` return hook. ### Verified - Confirmed dev-mode behavior with Vite 5 and Vite 8, including `exclude` handling on real image files. ## [2.2.0] - 2026-04-01 ### Changed - Added Vite 8 peer dependency support. - Scoped the plugin to dev server mode with `apply: "serve"`. - Switched path normalization to Vite `normalizePath`. - Moved watcher cleanup to the official `configureServer` return cleanup. - Made path comparisons case-insensitive only on Windows. - Added support for `public/...` paths when `publicDir` lives outside Vite `root`. - Made `exclude` resolution follow the same rules as watched folders. - Improved compatibility for Nuxt setups that use `srcDir` while keeping assets in the project-level `public/` directory. ### Documentation - Updated README with explicit Nuxt support notes and `srcDir` usage guidance. - Refreshed compatibility notes for Vite 4-8 and modern Node runtimes. ## [1.0.0] - 2024-10-28 ### Added - Initial release of the plugin. - Automatic image conversion to WebP. - Automatic image conversion to AVIF. - Chokidar-based file watcher for new files. - Configurable folders to watch. - Excluded folder support. - Optional AVIF generation. - Parallel WebP and AVIF processing. - Generated file detection to avoid conversion loops. - Detailed logging. - TypeScript declaration file. - Cross-platform path handling support.