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

@konsumer/useworker

v0.0.8

Published

Simple react hook for offloading work to another thread

Downloads

10

Readme

useWorker

This is a very simple react-hook for offloading work into another webworker-thread. It simplifies using web-workers, and doesn't require seperate JS files to define your worker.

Web workers have a slightly different API than plain browser stuff, so make sure to read about them.

Main consideration is that you can only pass values that are ok (JSONable, no functions, errors, etc, but File and Blob and more is ok) and you use postMessage in your onWork function to fire the onFinish. You can post multiple times, and it will each fire onFinish on each.

Use this whenever you can benefit from putting work in another thread, on the web. Inside the onWork thread, you can do fetch, web-sockets, OffscreenCanvas, and lots more. Think of it as "useEffect on another thread."

installation

npm i @konsumer/useworker

usage

You can see an example hook where I resize uploaded images in a worker.

Basic idea is like this:

import useWorker from '@konsumer/useworker'

// worker-side, called as worker. It can be a string or a function.
// Must be self-contained.
// It gets it's input from event.data, and outputs with postMessage
function onWork({data}) {
  // do whatever with data, in worker
  console.log(`useworker is ${data || 'amazing'}!`)
  postMessage('I finished.')
}

// host-side, called when worker does a postMessage
function onFinish(response) {
  // response is whatever onWork() called with postMessage()
  console.log(response)
}

// host-side, called when worker has an error
function onError(e) {
  console.error(e.message)
}

function MyThing() {
  // all params are optional
  const doStuff = useWorker ({ onWork, onFinish, onError })

  // call doStuff when you want to do work, it will send input arg as event.data
  doStuff('cool')

  return (
    <div>
      Check the console
    </div>
  )
}