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 🙏

© 2025 – Pkg Stats / Ryan Hefner

ntsk

v0.0.1

Published

Run tasks powered by Worker Threads in Node.js

Downloads

2

Readme

ntsk - Node Task

Run tasks powered by Worker Threads in Node.js

📦Install

This is a Node.js module available through the npm registry.

Before installing, download and install Node.js. Node.js 16 or higher is required.

npm

$ npm i -s ntsk

yarn

$ yarn add ntsk

Basic Usage

🟡JavaScript

const { task } = require('ntsk');

async function main(){
  const valA = 1; // scope variables are not accessible from task execution context
  const valB = 2;
  const result = await task(
    { valA, valB }, // define args to send to task execution context
    // define function code, is recommended to use async to define task functions
    async (_, { valA, valB }) => { 
      return valA + valB;
    }
  );
  console.log(result); // 3
}
main();

🔵TypeScript

import { task } from 'ntsk';

type MyTaskArgs = {
    valA: number;
    valB: number;
};

async function main() : Promise<void>{
  const valA: number = 1; // scope variables are not accessible from task execution context
  const valB: number = 2;
  const result: number = await task(
    { valA, valB }, // you should get full type completion
    async (_, { valA, valB } : MyTaskArgs) => { 
      return valA + valB;
    }
  );
  console.log(result); // 3
}
main();

Importing modules

It may be necessary to import modules in the task execution context, for this you can use the require function from the task execution context.

🟡JavaScript

const { task } = require('ntsk');

async function main(){
  const valA = 1;
  const valB = 2;
  const result = await task(
    { valA, valB }, 
    // first argument is reserved for task execution context helpers
    async ({ require }, { valA, valB }) => { 
      const math = require('./math'); // import your own module at task execution context
      return math.sum(valA, valB);      
    }
  );
  console.log(result); // 3
}
main();

🔵TypeScript

import { task } from 'ntsk';

type MyTaskArgs = {
    valA: number;
    valB: number;
};

async function main() : Promise<void>{
  const valA: number = 1;
  const valB: number = 2;
  const result: number = await task(
    { valA, valB },
    // first argument is reserved for task execution context helpers
    async ({ require }, { valA, valB }) => { 
      const math = require('./math'); // import your own module at task execution context
      return math.sum(valA, valB);      
    }
  );
  console.log(result); // 3
}
main();

Directory and File references

If you are running any file I/O operation chances are you want to keep as reference the __dirname and __filename variables of the script that triggered the task execution. These values are available through the task execution context.

🟡JavaScript

const { task } = require('ntsk');

async function main(){
  console.log(__dirname); // /home/user/my-project/src
  console.log(__filename); // /home/user/my-project/src/index.js

  await task(null,     
    async ({ __filename, __dirname }) => { 
      console.log(__dirname); // /home/user/my-project/src
      console.log(__filename); // /home/user/my-project/src/index.js
    }
  );
}
main();

🔵TypeScript

import { task } from 'ntsk';

async function main() : Promise<void>{
  console.log(__dirname); // /home/user/my-project/src
  console.log(__filename); // /home/user/my-project/src/index.js

  await task(null,     
    async ({ __filename, __dirname }) => { 
      console.log(__dirname); // /home/user/my-project/src
      console.log(__filename); // /home/user/my-project/src/index.js
    }
  );
}
main();

🔑License

MIT