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

@futils/multi-threading

v1.0.0

Published

A simple multithreading library

Downloads

2

Readme

multi-threading

Issues and Pull Requests

Usage

where you want to use the thread:

import { startThread } from '@futils/multi-threading';

const thread = startThread<
    'log' | 'eval',
    { log: string; eval: string },
    { log: void; eval: any }
>('./<filename>.js');

export type standardThread = typeof thread;

the thread script:

import { standardThread } from './<thread-launch-scriptname>';
import { getThreadProcess } from '@fuilts/multi-threading';

const thread = getThreadProcess<standardThread>();

Interface for the thread launcher

  • send(channel, data): Promise<returnedData>: This will send a message to the thread. The channel is the first type provided to startThread, the data the second and the returnedData the 3rd
  • kill(): This will kill the thread
  • onMessage(message, (data: returnedData)): () => {}: This will register a messagelistener for a particular message. message is the first type provided to startThread, returnedData the 3rd. It returns a function, that when called, unregisters the listener
  • onMessageOnce(message, (data: returnedData)): () => {}: This will register a messagelistener for a particular message. message is the first type provided to startThread, returnedData the 3rd. It returns a function, that when called, unregisters the listener. The listener gets automatically removed after it got triggered once.
  • removeListener(message, cb): This will remove a onMessage and onMessageOnce listener. The cb has to be the same function, not just one that has the same behavior and contents
  • isRunning(): boolean: Tells you if the thread is still running
  • stop(): Stops the thread
  • whenExit(): This will resolve when the thread exits, or immediately if its not running
  • whenReady(): This will resolve when the thread is ready, or immediately if its running and already ready.

Interface for the thread client (script)

  • send(message, data): This will send a message to the thread launcher. message is the first type provided to startThread, and data the 3rd
  • onMessage(message, (data) => returnedData|Promise<returnedData>): This will listen for a message. message is the first type provided to startThread, data the 2nd and returnedData the 3rd. It returns a funtion, that when called, unregisters the listener.
  • onMessageOnce(message, (data) => returnedData|Promise<returnedData>): This will listen for a message. message is the first type provided to startThread, data the 2nd and returnedData the 3rd. It returns a funtion, that when called, unregisters the listener. The listener gets automatically removed after it got triggered once.
  • removeListener(message, cb): This will remove a onMessage and onMessageOnce listener. The cb has to be the same function, not just one that has the same behavior and contents