npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

worky-turkey

v1.0.1

Published

call functions in web worker from main thread (et vice versa)

Downloads

6

Readme

worky-turkey

call functions in web worker from main thread (et vice versa)

Usage

index.html

<button type="button" id="counter"></button>
<script src="wokry-turkey.min.js"></script>
<script>
  const counterButton = document.getElementById('counter')
  const worker = workyTurkey.expose(
    {
      // the `render` function will be available in the worker
      render (value) {
        counterButton.textContent = value
      }
    },
    new Worker('worker.js')
  )

  counterButton.addEventListener('click', function () {
    // call the `increment` function exposed by the worker
    worker.increment()
  })
</script>

worker.js

loadScripts('worky-turkey.min.js')
let counter = 0;

const ui = workyTurkey.expose({
  // the `increment` function will be available in the main thread
  increment(value = 1) {
    counter += value
    // call the `render` function exposed by the ui thread
    ui.render(counter)
  }
});

// call the `render` function exposed by the ui thread
ui.render(counter)
…

Browser support

worky-turkey uses proxies, whose are supported in all evergreen browsers: caniuse proxy

But...

What's about Comlink?

worky-turkey is heavily inspired by Comlink. But there are use cases, you just don't need the super power of Comlink.

Comparend to Comlink, worky-turkey...

  • only supports function calls
  • does not return anything (just fire and forget)
  • does not support callbacks as function parameter (just Transferables. As rule of thumb: only use primitives, plain objects and arrays as parameter)
  • is written in less than 25 lines of code 😎 (~300 bytes minified, ~240 bytes gzipped)

This is great if you just want the other side know, that something has to be done.
This is not so great if you rely on the result of the other sides function call.

Why do I need a library for this simple task?

Of course, you can postMessage something like { fn: 'doSomething', params: ['foo', 42] } and handle it accordingly on the other side, but it simply feels more naturally to call worker.doSomething('foo', 42).