Support custom `stdout` and `stderr` about wasm-vips HOT 5 CLOSED

I just cherry-picked that PR in the emscripten-core/emscripten@3.1.29...kleisauke:wasm-vips-3.1.29 changeset with commit kleisauke/emscripten@cf6cdde.

This will be in v0.0.5.

from wasm-vips.

Upstream PR: emscripten-core/emscripten#18163.

from wasm-vips.

v0.0.5 now available.

from wasm-vips.

Hi @atjn,

It looks like a bug in Emscripten's NODERAWFS filesystem backend, on the web this works properly:

import Vips from 'wasm-vips';

const log = (type, text) => console.log(`${type}: ${text}`);
const vips = await Vips({
  print: (text) => log('stdout', text),
  printErr: (text) => log('stderr', text),
  preRun: (module) => {
    // Handy for debugging
    // module.ENV.VIPS_INFO = '1';
    // module.ENV.VIPS_LEAK = '1';

    // Hide warning messages
    module.ENV.VIPS_WARNING = '0';
  }
});

For now, I can recommend setting the VIPS_WARNING environment variable, as shown in the example above.

Upstream issue: emscripten-core/emscripten#17688

from wasm-vips.

Thank you so much for the absolutely excellent debug work here!

from wasm-vips.