# Any thin wrapper around the Web Worker API?

**URL:** <https://users.rust-lang.org/t/any-thin-wrapper-around-the-web-worker-api/142888>\
**Category:** help\
**Created:** [October 7, 2026, 3:33pm UTC](https://users.rust-lang.org/t/any-thin-wrapper-around-the-web-worker-api/142888 "2026-10-07T15:33:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![iFrostizz](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/ifrostizz/32/36548_2.png) [@iFrostizz](https://users.rust-lang.org/u/iFrostizz)\
**Post date:** [October 7, 2026, 3:33pm UTC](https://users.rust-lang.org/t/any-thin-wrapper-around-the-web-worker-api/142888/1 "2026-10-07T15:33:44Z")

</div>

Hi, I'm currently writing some audio decoding pipeline targeting wasm32-unknown-unknown.  
In the queue / jittering part, I wanna be able to have one task that pushes data as it comes (with all the network uncertainties), and another parallel task that reads data from this buffer. On a native platform, a naive solution would be to use tokio tasks with a mutex around the buffer. Obviously this is not possible in WASM as-is.  
Is there any crate that interfaces with the Web Workers API? The most idiomatic (as in matching the API as opposed to match tokio style) the better.  
Thanks!