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

sandbox-worker

v1.2.0

Published

securely run untrusted JS functions in an isolated quickjs runtime inside a worker thread

Downloads

16

Readme

sandbox-worker

const SandboxWorker = require('sandbox-worker')

const {addTask, end} = SandboxWorker(onEnd)

function onEnd(err) {
  if (err == true) {
    console.error('worker ended normally')
  } else if (err) {
    console.error(`worker crashed: ${err.message}`)
  }
}

// pass code as a string
// it must be a commonJs module exporting a funtion with one parameter
const task = addTask(`
  const c = 10
  module.exports = function ([a, b]) {
    return a + b + c
  }
`)

// pass arguments as JSON strings
task('[5, 6]', (err, result) =>{
  console.log(result) // => '21'
  task.remove( err=>{
    // if you are done, call end()
    end( err=>{})
  })
})

WOrks in Electron (testec with Electron 8.2.3)

Why passing arguments as JSON strings?

The arguments have to be serialized to be sent to the worker. In cases where your input data already is JSON, we save a redundant JSON.stringify()/JSON.parse() rondtrip this way.

API

SandboxWorker(onEnd)

creates a new worker thread

  • onEnd: a callback that is called when the worker exits. The callback is called with true when the thread ended normally, and with an Error object otherwise.

returns an object with two properte:

  • addTask: a function that lets you add a function to the worker
  • end: a function that allows you to explicitly end the worker's execution

addTask(code)

Creates a new JS runtime and JS execution context and adds a task to the worker. You can add multiple tasks to the same worker. They will be isolated from each other and will be executed in sequence (not in parallel) when invoked.

  • code: a commonJS module's source code.

The code must assign a function that takes one argument to module.exports. That function can be called by calling the return value of addTask.

returns: an async function taking one argument as a JSON string. The JSON string will be deserialized inside the worker and the task will be executed by calling module.exports with the deserialized JSON.

  • task(argument, cb)
    • argument: JSON string to be used as function argument
    • cb: errback, called with the result of the taks invokation

end(cb)

ends the worker thread.

See tests for details.

License: MIT