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

rollup-plugin-worker-factory

v0.5.7

Published

Bundle web workers that work in nodejs and the browser, without a separate build target.

Downloads

1,102

Readme

Install

npm i -D rollup-plugin-worker-factory

Requirements

  • browsers with web worker support (tested in ie 11)
  • nodejs >= 10 when node is run with --experimental-workers
  • natively in nodejs >= 12 without any arguments to node

Usage

include rollup-plugin-worker-factory in your rollup plugins array for a build:

const worker = require('rollup-plugin-worker-factory');

...
plugins: [
  worker()
]
...

When you want to include a worker in your code prefix the file with worker!:

import SomeWorker from "worker!./src/some-worker.js";

Your worker should run without exporting any code and use the global self variable to interact with the worker API. worker_threads.parentPort for node has been slightly modified so that their API more closely matches web workers in the browser and will also be available on the global self.

const someDependency = require('../some-dep');
const whoKnows = require('who-knows');

self.addEventListener('message', function(e) {
  const foo = someDependency(e);

  self.postMessage(whoKnows(foo));
});

How it works

  1. We use rollup to rollup all dependencies for your web worker file into a bundle.
  2. We wrap that rollup in a function so that it can be minified and included normally in your code without doing anything.
  3. We return a web worker constructor for your function that will run in the web worker with slight modifications to unify the API (nothing that you, the user should have to worky about).

Modifications to node worker_threads

  • We mirror on to addEventListener on worker objects
  • We mirror off to removeEventListener on worker objects
  • We wrap postMessage so that the message sent is included as a value for a data key on an object as this is how the browser works with postMessage.

Modifictaion to browser WebWorkers

  • We automagically create a blob url of your code to run in the worker that will be revoked on worker terminate
  • We mirror addEventListener to on on worker objects
  • We mirror removeEventListener to on on worker objects
  • We add the created blob url to the worker as an objURL property

Options

plugins

An array of rollup plugins to bundle the web workers with, you will probably want:

type

Default: 'universal'

The type of factory to build, can be 'node', 'mock', 'browser', or 'universal'.