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

comlink-everywhere

v0.2.7

Published

This is a workaround to help patch inconsistent environments until module workers (and eventually [module block](https://github.com/tc39/proposal-js-module-blocks) workers) are available everywhere. Module workers are:

Downloads

5

Readme

comlink-everywhere

This is a workaround to help patch inconsistent environments until module workers (and eventually module block workers) are available everywhere. Module workers are:

  • Available in Chromium-based browers, node (with an API significantly differing from all other environments), and deno.
  • Implemented in Safari, but probably not available on iOS until iOS 15.
  • In progress for Firefox

It also helps test bundler compat issues like snowpackjs/snowpack#3476

Usage

// index.js
import { workerFileConstructor, wrap } from "comlink-everywhere/outside";

(async () => {
  const Worker = await workerFileConstructor();
  const api = wrap(
    new Worker(new URL("./worker.js", import.meta.url), { type: "module" })
  );
  console.log(await api.add(3, 4));
})();
// worker.js
import { expose } from "comlink-everywhere/inside";

expose({
  add: (x, y) => x + y,
});

Construct from string

import { constructWorkerFromString } from "comlink-everywhere/outside";

(async () => {
  const worker = await constructWorkerFromString(
    // Note: this example only works in browsers.
    `self.postMessage("from worker");`
  );
  worker.addEventListener("message", (message) => console.log(message.data));
})();

For maximum compatibility in the short term, the best option is to compile the worker into a source string that does not use any imports, and does not use any syntax or functions specific to CommonJS (e.g. require()), ESM (e.g. import), or the web (e.g. importScripts())

Tradeoffs

  • If you're running node , the type option will be ignored and the worker will be instantiated as a classic/module worker matching the calling code. See https://github.com/nodejs/node/issues/30682
  • This library is written as ESM. It is only meant to be used with ESM, except specifically for workers instantiated from strings (as a workaround for Firefox and Safari's lack of module worker support).
  • The Worker constructor cannot be retrieved synchronously.
    • The implementation uses a dynamic import to get the node constructor for better compatibility (by not importing node modules unless necessary), which means it is not available synchronously.
  • .terminate() is not currently available on node workers. Please file an issue if you want to use this library and be able to call .terminate().
    • Note that we always call .unref() for node workers, which means they will not hold up program exit.