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

wasi-worker

v0.1.1

Published

Node.js worker for running WASI code

Downloads

2

Readme

wasi-worker

Current Version Dependencies belly-button-style

Run WASI code inside of a Node.js Worker.

Note: WASI as a technology is still experimental. The WASI APIs in Node.js are also considered experimental and subject to change. For best results, use this module with the most recent version of Node.js.

Usage

The following example demonstrates how wasi-worker is used to create Node.js Worker threads executing WASI nanoprocesses.

'use strict';
const { createWasiWorker } = require('wasi-worker');
// worker is a Worker instance from the Node.js worker_threads module.
const worker = createWasiWorker({
  args: ['foo', '-bar', '--baz=value'],
  env: { ...process.env },
  preopens: { '/sandbox': '/tmp' },
  timeout: 10000,
  wasmFile: 'app.wasm'
});

worker.on('exit', (code) => {
  console.log('wasi worker exited with code:', code);
});

API

This section describes the complete wasi-worker API.

createWasiWorker([options])

  • Arguments
    • options (object) - Optional configuration object supporting the following schema:
      • args (array) - An array of strings that the WebAssembly application will see as command line arguments. Optional. Defaults to [].
      • env (object) - An object similar to process.env that the WebAssembly application will see as its environment. Optional. Defaults to {}.
      • preopens (object) - This object represents the WebAssembly application's sandbox directory structure. The string keys of preopens are treated as directories within the sandbox. The corresponding values in preopens are the real paths to those directories on the host machine. Optional. Defaults to {}.
      • resourceLimits - (object) - An object representing the resource limits imposed on the worker thread. This object is passed verbatim to the Worker constructor. Optional. Defaults to {}.
      • timeout (number) - The maximum number of milliseconds that the WebAssembly may execute for. If the thread has not exited before the timeout has elapsed, the thread is terminated. Optional. Defaults to no timeout.
      • wasmFile (string) - The path to the .wasm file to load and execute.
  • Returns
    • An instance of a Node.js Worker thread.

Executes a WASI application inside a Node.js Worker thread. The returned thread has exactly the same API as one created via Node's Worker constructor.