Ahhh, I just saw this thread, thanks for this information.
Somehow I asked a similar question yesterday: Building WASM Opencv.js: 'cv' is a Promise, not an Object
It seems that:
-
public-facing opencv.js builds use ‘cv’ as Object, and the WASM version requires further initialization through cv[‘onRuntimeInitialized’], as described here: javascript - cv.Mat is not a constructor opencv - Stack Overflow
-
manual opencv.js builds (as you and me experienced) show that, now, ‘cv’ is a Promise. onRuntimeInitialized no longer applies - seems like it.
Anyone know what arguments might’ve been used while building the downloadable opencv.js to get it to work like this?
Did you get an explanation for the difference of behavior?