Can textureResize become textureCompress on the web?

[elalish]

Is your feature request related to a problem? Please describe.
I'd like to compress jpg/png textures into webP on the web. textureCompress is the function I want, but it doesn't (yet) work on the web. textureResize does work on the web, but only supports jpg/png and apparently not converting between them.

Describe the solution you'd like
Looking at your ndarray-pixels package, it seems like textureResize would be able to do everything textureCompress does if this check were removed (at least on web) and the options were added. Is there any reason not to?

Describe alternatives you've considered
Wait for sharp to add web support.

Additional context
I'd like to take a stab at making a very simple, very automatic glTF optimizer based on gltf-transform, probably living next to the model-viewer editor.

[donmccurdy]

I'm not using very much of the Sharp API, I wonder if we could 'polyfill' Sharp with a small wrapper around ndarray-pixels, and use it as a fallback to the Sharp API? Would just need to match the API here:

glTF-Transform/packages/functions/src/texture-compress.ts

Lines 132 to 147 in 482a718

	const srcImage = texture.getImage()!;
	const instance = encoder(srcImage);
	// Convert if target and source formats differ.
	if (srcMimeType !== dstMimeType) {
	instance.toFormat(dstFormat);
	}
	// Resize.
	if (resize) {
	instance.resize(resize[0], resize[1], {
	fit: 'inside',
	kernel: resizeFilter,
	withoutEnlargement: true,
	});
	}

An alternative here would be https://github.com/kleisauke/wasm-vips ... same underlying native library as Sharp, compiled to WASM, but note the "early development" disclaimers. I tend to assume the compression with libvips is better than what browsers provide, but I don't really know on that.

[elalish]

Yes, I guess I thought most of the code for that polyfill was already in textureResize. Perhaps those two functions could be combined, thus providing the fallback with a single API? I have no problem with browser-level compression, so long as we can go from lossless to lossy.

[donmccurdy]

Maybe just removing textureResize would be the thing to do, yeah. Can't resize without recompressing anyway. Smaller/simpler API surface to maintain. Then let textureCompress default to ndarray-pixels if no encoder is given, so it works on the web out of the box.