…ings

…n, transparency check and resizing

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

This commit implements output format conversion for client-side media
processing, enabling generation of modern image formats (AVIF, WebP)
and modern JPEG codecs (MozJPEG) during upload.

Key changes:

- Add TranscodeImage operation type for format conversion
- Add imageOutputFormats, jpegInterlaced, pngInterlaced, gifInterlaced
  settings that flow from PHP REST API through the settings stack
- Implement transcodeImageItem action using vipsConvertImageFormat
- Update prepareItem to check format mapping and add TranscodeImage
  operations when needed
- Add transparency check for PNG->JPEG to preserve alpha channels
- Apply format conversion to generated thumbnails
- Add MozJPEG optimizations (optimize_coding, quant_table) for JPEG
  output, providing ~10-15% smaller file sizes

The implementation respects WordPress's image_editor_output_format
filter for format mapping configuration.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

- Fix blob URL memory leak using try/finally pattern for transparency check
- Add format validation before ImageFormat type assertion
- Improve JSDoc for Settings interface properties
- Add clarifying comment for empty filename in image_editor_output_format filter

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

The preload filter was using str_replace to insert media fields after
"home,", but this pattern-based approach could fail if WordPress's
preload path had a different field order. This caused an extra REST
API request to the root endpoint in the site editor.

Replace the entire _fields parameter with the complete list expected by
packages/core-data/src/entities.js to ensure exact URL match for preloading.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

…-lock-trunk' into feature/client-side-media-dev

The ES6 version of wasm-vips uses import.meta for path resolution,
which requires the worker to be created as a module worker.
Classic script workers (the default) don't support import.meta,
causing the WASM module to fail loading with an undefined error.

By adding { type: 'module' } to the Worker constructor, import.meta
becomes available, and the ES6 version's locateFile callback works
correctly with our base64 data URL approach.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Merges the module worker type fix while keeping the preload paths function.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

This reverts commit b1779c4.

Add esbuild plugin to redirect wasm-vips ES module (vips-es6.js) to
CommonJS version (vips.js) which doesn't use import.meta.url that fails
in Blob URL Worker context.

Also:
- Upgrade wasm-vips from ^0.0.10 to ^0.0.16
- Add vips-heif.wasm inline import and locateFile handler

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Set DEBUG_ENABLED to false to prevent unexpected console.log
calls that cause test failures with @wordpress/jest-console.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Move media processing fields (image_output_formats, jpeg_interlaced,
png_interlaced, gif_interlaced) from a filter in load.php to the
template files directly. This simplifies the code path and ensures
the preload paths match exactly with entities.js.

- Add fields to page.php.template and page-wp-admin.php.template
- Remove gutenberg_media_processing_preload_paths filter from load.php
- Update @see references in entities.js

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>