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

chrome-killer

v2.2.1

Published

Kill all Chrome/Chromium tabs or entires to improve performance, decrease battery usage, and save memory

Downloads

9

Readme

chrome-killer (from kill-tabs)

Kill all Chrome/Chromium tabs or entires to improve performance, decrease battery usage, and save memory

Works on macOS, Linux, Windows.

When you run kill-chrome the Chrome tab processes are killed, which means they will no longer take up system resources, but they will still be in your Chrome window, just as crashed. When you want one back you just reload the tab.

CLI

$ npm install --global chrome-killer
$ chrome-killer --help

  Usage
    $ chrome-killer

  Options
    --no-chromium            Don't kill tabs in Chromium
    --no-chrome              Don't kill tabs in Chrome
    --including-main-process Kill main browser process
    --instance-path          Specify path of Chrome/Chromium instance to kill

API

$ npm install --save chrome-killer
const chromeKiller = require('chrome-killer');

chromeKiller().then(() => {
	console.log('Killed tabs');
});

Tip

You can use the Reload All Tabs Chrome extension to easily reload all the tabs.

License

MIT © Sindre Sorhus MIT © Lu Yuan