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

better-tasklist

v1.2.0

Published

A new wrapper for the Windows `tasklist` command. Gives developers the ability to control running tasks.

Downloads

18

Readme

better-tasklist

A Javascript written wrapper for the Windows tasklist command. better-tasklist gives developers the ability to control running windows tasks. Inspired by @sindresorhus's tasklist wrapper, tasklist.


Installation

Installing better-tasklist can be done using the following command down below.

$ npm install better-tasklist

You might need to install csv-parser as well. That can also be done by the following command down below.

$ npm install csv-parser

Usage

import tasklist, { FilteredWindowsProcesses, FetchedWindowsProcesses } from "better-tasklist";

(async function() {
    // Start writing your program here.

    // The verbose property is optional which will return detailed results.
    const processes: FetchedWindowsProcesses = await tasklist.fetch({verbose: true}); 

    // Returns an array with fetched Windows processes that has the name 'svchost.exe'.
    const filtered: FilteredWindowsProcesses = await tasklist.filter(processes, {
        imageName: "svchost.exe"
    });

    console.log(filtered);
    /* Returns an array with objects like this
    {
        imageName: 'svchost.exe',
        pid: '6969', // Nice number
        sessionName: 'Services',
        sessionNumber: '0',
        memUsage: '6.412 K',
        status: 'Unknown',
        username: 'N/A',
        cpuTime: '0:00:00',
        windowTitle: 'N/A'
    }
    */
})();

API usage

fetchAllProcesses(options, events);

.fetch(options: FetchingOptions | null, events?: FetchingEvents) => Promise<FetchedWindowsProcesses | WindowsProcess[]>;

Retrieves all active and inactive processes. The options are optional.

The options parameter has to be either null or FetchingOptions. Use null to skip this paramater.

filterFetchedProcesses(fetchedProcesses, filter);

.filter(fetchedProcesses: FetchedWindowsProcesses, filter: FilteringKeywords): FilteredWindowsProcesses | WindowsProcess[];

Filters one or more processes based on the given filter name.

The fetchedProcesses parameter is a reference to FetchedWindowsProcesses. The filter parameter is a reference to FilteringKeywords object.

killProcessByPID(pid);

.killProcessByPID(pid: string | number, force?: boolean): Promise<ExecutionSignals | Error>;

Stops an active Windows process. If the process cannot be stopped, try forcing it.

The force parameter (boolean) is an optional parameter, forcing killing the process.

Examples

import tasklist, { IEnumeratedProcesses } from "better-tasklist";

(async function () {

    // Fetching active Windows processes the fast way.
    const normal: WindowsProcess[] = await tasklist.fetch({ verbose: false });

    // Fetching both all active and inactive Windows processes the slow way.
    const verbose: WindowsProcess[] = await tasklist.fetch({ verbose: true });

    console.log(`Retreived ${normal.length} non-verbose processes.`);
    console.log(`Retreived ${verbose.length} verbose processes.`);
})();
import tasklist, { FetchedWindowsProcesses } from "better-tasklist";

(async function () {

    const fetchedProcesses: FetchedWindowsProcesses = await tasklist.fetch({ verbose: false });

    const filteredProcesses = await tasklist.filter(fetchedProcesses, {
        imageName: "Discord.exe"
    });

    console.log(filter);
})();
import tasklist, { FetchedWindowsProcesses, WindowsProcess } from "better-tasklist";

(async function () {

    const fetchedProcesses: FetchedWindowsProcesses = await tasklist.fetch({ verbose: false });

    const filteredProcesses = await tasklist.filter(fetchedProcesses, {
        imageName: "Among us.exe"
    });


    filteredProcesses.forEach(function(windowsProcess: WindowsProcess) {

        tasklist.killProcessByPID(fetchedProcess.pid, true);
    });
})();

Help and other related things

If there are any bugs, or things that makes no sense (most likely), feel free to create an issue and I'll fix it.