Sebastian Alff

There's probably quite a bit of overhead involved with threading, since that's not natively supported in WASM ([yet](https://github.com/WebAssembly/proposals)) and Emscripten basically does a work-around using web workers. I would expect...

[Here](http://quaoar.su/blog/page/indexing-the-topology-of-opencascade) is an interesting article on that subject, that dives a bit deeper into the underlying issues.

I'm encountering the same issue. Has anyone found a workaround for this?

Thanks a lot for the clarification. I had already realized that I was just using the library in the wrong way. I'm just starting with a bit of a deeper...

Having the same issues. I was also expecting this to work as shown in the original issue, based on the documentation and the fact that you could insert `beforeInteractive` scripts...

...I also just ran into this problem.

Just wanted to give my +1 for this request. (I'm having a "brownfield" project, which is already using react-query@5 and I tried using refine there. It looks like the missing...

Thanks @PapyElGringo for your great work on this project. > Since it's still planned to work on our own WM is the short future I'm not sure I'll dig into...

> For those who are interested, we are now using a static ip in our cloud functions. Did not solve every problem but it helped to reduce them a lot....

I would also love to see this feature in NodeJS. My ~45MB WASM project starts reasonably fast in the browser, but takes minutes to start up in NodeJS. Given that...