[v4] suppress console.error while creating InferenceSession

[nico-martin]

I invested some time into #1236 and from what I see there are three ways how we could solve this:

1. suppress console.error while creating InferenceSession
2. while copying the wasm .mjs file we could overwrite the line that cases the console.error
3. change the wasm library .mjs file.

for 3. We (or the ONNX maintainers) would have to make changes directly in their library. This would certainly be the cleanest solution, but we would be dependent on third parties. 2. I would not recommend this, as it could disrupt the copying process if changes are made within the ONNX library.
That's why solution one would be my favorite. It looks a bit messy or hacky, but honestly, I think it's the simplest solution.

[xenova]

Thanks for the PR! I recall that for V3, the inference session logging options would not work

[logSeverityLevel](https://onnxruntime.ai/docs/api/js/interfaces/InferenceSession.SessionOptions.html#logSeverityLevel)?: 0 | 2 | 1 | 3 | 4;
    [logVerbosityLevel](https://onnxruntime.ai/docs/api/js/interfaces/InferenceSession.SessionOptions.html#logVerbosityLevel)?: number;

but perhaps they work now? https://onnxruntime.ai/docs/api/js/interfaces/InferenceSession.SessionOptions.html

---

We can then set a global default logging behaviour, without needing to override global console methods.

[nico-martin]

Unfortunately this does not work. Even with logSeverityLevel:4, logVerbosityLevel:4 I still get this console.error

I think it does make sense to set the logSeverityLevel: 4.

But for the Unknown CPU vendor. cpuinfo_vendor value: 0 error, I had to dig deeper.
This is actually thrown here: https://github.com/microsoft/onnxruntime/blob/main/onnxruntime/core/common/cpuid_info_vendor.cc#L239
I think thats a) expected behaviour because when running in WebAssembly in a browser, the code doesn't have access to CPU vendor information and b) not an issue at all.

This warning actually bypasses the session-specific settings.
But after a lot of further digging in the onnxrunntime I found out there is a ONNX_WEB.env.logLevel. So when this is set to fatal, it wont show up in the console :)

[nico-martin]

My solution now sets the default logging level to 4 (fatal). But it can be overwritten with session_options.logSeverityLevel

const segmenter = await pipeline("background-removal", "Xenova/modnet", {
  device: "webgpu",
  session_options: {
    logSeverityLevel: 2, // warning
  },
});

Tis will not only set the onnxrunntime session_options, but also the ONNX_WEB.env.logLevel

[xenova]

I think we can move the ONNX_WEB.env.logLevel logic to happen during init (similar to how we set default WASM paths (as a good default).

This should hopefully minimize any session_options specific code a user would need to set.

[nico-martin]

I actually think it makes sense to set the ONNX_WEB.env.logLevel here where I create a new session. Als a transformers.js user I dont really care if the log is a "onnxruntime session log" or a "onnxruntime general log". All I want to do is to create a pipeline and then be able to set the logLevel.
My solutions basically abstracts this decision away by only providing one setting and thats basically the settings that has always been available in the session_options (although very view people actually used that setting in the past I guess).

[xenova]

this should be good. From my testing, a value of 3 will hide

2025-12-03 00:44:48.937 node[68874:20600323] 2025-12-03 00:44:48.937479 [W:onnxruntime:, session_state.cc:1316 VerifyEachNodeIsAssignedToAnEp] Some nodes were not assigned to the preferred execution providers which may or may not have an negative impact on performance. e.g. ORT explicitly assigns shape related ops to CPU to improve perf.
2025-12-03 00:44:48.937 node[68874:20600323] 2025-12-03 00:44:48.937528 [W:onnxruntime:, session_state.cc:1318 VerifyEachNodeIsAssignedToAnEp] Rerunning with verbose output on a non-minimal build will show node assignments.

but as you say in #1468 (comment), a value of 4 is necessary to hide everything else when running in browser.