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

concurrent-plugin-js

v0.1.3

Published

Run wrapper concurrently using promise

Downloads

1

Readme

Concurrency

It allows wrappers to subinvoke multiple wrappers concurrently.

This library has been implemented in an easily extensible way. It provides a common concurrency interface that can be shared across various concurrency implementations, like Threads, Processes and even language specific primitives like JavaScript Promises. We have already implemented the promise plugin implementation and will be adding more such implementations for primitives like threads and processes.

Usage

  • If you are a Wrapper Developer - You just need to import the Concurrent interface, and you can get all the implementations that the client has registered in the wrapper using Interface.getImplementations function. You can use one or all of them to schedule the sub-invocations concurrently and get the result asynchoronously. Alternatively, you can specify the uri of the particular implementation that you want to support.

    • Schema

      #import * into Interface from "wrap://ens/interface.concurrent.polywrap.eth"
      #use { getImplementations } for Interface
      
      type Module{
        foo(tasks: [Interface_Task!]!): Boolean!
      }
    • Wasm-as

      import { 
        Interface,
        Interface_Module,
        Args_foo 
      } from "./wrap";
      
      export function foo(args: Args_foo) {
        const impls = Interface.getImplementations();
        if (impls.length < 1) {
          throw new Error("...")
        }
        const concurrent = new Interface_Module(impls[0]);
      
        const taskIds = concurrent.schedule(args.tasks);
      
        ...
      
        const results = concurrent.result(taskIds);
      }
  • If you are an App Developer - You need to register the implementations of the Concurrent interface using the client config.

const config = {
  ...,
  plugins: [
    ...
    {
      uri: "wrap://ens/promise.concurrent.polywrap.eth"
      plugin: ConcurrentPromisePlugin()
    }
  ]
  interfaces: [
    {
      interface: "wrap://ens/interface.cache.polywrap.eth",
      implementations: [
        "wrap://ens/promise.concurrent.polywrap.eth",
        ...
      ]
    }
  ]
}