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

@phylum/worker-task

v3.0.0-beta.0

Published

Move tasks that are computationally heavy or use synchronous io to a worker thread

Downloads

3

Readme

worker-task

Move tasks that are computationally heavy or use synchronous io to a worker thread.

Installation

npm i @phylum/worker-task

Please note that node worker threads are currently experimental!

# In order to enable worker thread support, you
# have to pass the following flag to node:
node --experimental-worker ...

Usage

When a worker task is executed, it will create a new worker thread, load the specified entry module and run the exported task in an independent pipeline.

createWorkerTask(filename[, options])

// parent.js
const {createWorkerTask} = require('@phylum/worker-task')

const task = createWorkerTask(path.join(__dirname, 'worker'))
// worker.js
module.exports = async ctx => {
	console.log('Hello World!')
}
  • filename <string> - The filename of the worker entry. This can be relative to the current working directory.
  • options <object> - An object with the following options:
    • stdin, stdout, stderr, execArgv - See worker options
    • onDispose - Set how to dispose the worker:
      • 'disable' - Default. Disable the worker pipeline.
      • 'terminate' - Terminate the worker thread. (Not recommended)

Serialization

By default, errors are converted to strings using util.inspect(..) before passing them to the parent thread and results are not passed at all. You can use the v8 serialization api by wrapping a value into a Serializable instance. However if the wrapped value is not serializable, an error will be passed to the parent thread.

// worker.js
const {Serializable, raw} = require('@phylum/worker-task')

module.exports = async ctx => {
	return new Serializable({foo: 'bar'})

	// Or use the shorthand function:
	return raw({foo: 'bar'})
}