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

@wix/editor-platform-transport

v1.10.0

Published

- Browser – Worker – Browser - Browser – Frame – Browser

Downloads

746

Readme

Communication between threads

  • Browser – Worker – Browser
  • Browser – Frame – Browser

🏆🏆🏆

  • Transferred API completely copies the transferred objects, so no proxies. This allows to correctly decorate received APIs.
  • No additional utils needed, like comlink.wrap or comlink.proxy
  • Supports passing promises and callbacks between threads without wrapping it with additional decorators
  • Supports catching errors between threads (see src/demo)
  • Super small ~3kb

Worker

import {ConsumerChannel} from '@wix/editor-platform-transport';


const channel = new ConsumerChannel();

class WorkerAPI {
  type = 'WORKER_API';

  functionWithCallback(cb: Function) {
    cb(new Promise(resolve => {
      setTimeout(() => {
        resolve('xxx')
      }, 1000)
    }));
  }
}

channel.expose(new WorkerAPI());

Browser

import {HostChannel} from '@wix/editor-platform-transport';

const worker = new Worker('../dist/statics/demo/worker.js');

const channel = new HostChannel(worker);
channel.recieve<WorkerAPI>('WORKER_API', async api => {
  /**
   * api - object, exposed from the worker
   * it is shape in the main thread is exactly the same as in the worker,
   * so we can easyly decorate it or proxify, for example for tracing
   */
  await api.functionWithCallback(async (promiseFromWorker) => {
    console.log('main-thread', await promiseFromWorker)
  })
})

This example will output `'main-thread xxx' after 1sec.

Expose Multiple APIs

import {ConsumerChannel} from '@wix/editor-platform-transport';


const channel = new ConsumerChannel();

class WorkerAPI {
  type = 'WORKER_API';
}

class ApplicationAPI {
  type = 'APPLICATION_API';
}

channel.expose(new WorkerAPI());
channel.expose(new ApplicationAPI());