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

why-is-node-still-running

v1.0.0

Published

Find out exactly why Node is still running.

Downloads

1,530

Readme

🏃 why-is-node-still-running

License Latest release Coverage status

This is a port of mafintosh' why-is-node-running module to TypeScript, with modernized syntax and no dependencies.

const { whyIsNodeStillRunning } = require('why-is-node-still-running');
const { createServer } = require('net');

const server = createServer();
server.listen(0);

whyIsNodeStillRunning();
// There are 2 handle(s) keeping the process running

Installation

npm i -D why-is-node-still-running

Usage

Always import this module first so that the asynchronous hook can be setup. The hook will log to the console by default, but you can provide it with a custom logger that implements error().

Example of usage with Jest

Sometimes Jest complains that there are asynchronous operations still hanging after the tests have been completed. When the --detectOpenHandles flag gives no output, you can try using this module to help pinpoint the cause:

import { whyIsNodeStillRunning } from 'why-is-node-still-running';

afterAll(async () => {
	// Do your actual cleanup here
	// [...]

	// Print the handles still opened
	await new Promise(resolve => setTimeout(() => {
		whyIsNodeStillRunning();
		resolve();
	}, 4000));
});

Don't forget to run Jest with --useStderr to show console output.

Alternatively, you can use this module to print some information about the stack regularly while the tests are running (e.g. see this comment).

License

Copyright (c) 2020-present, cheap glitch

Permission to use, copy, modify, and/or distribute this software for any purpose
with or without fee is hereby  granted, provided that the above copyright notice
and this permission notice appear in all copies.

THE SOFTWARE  IS PROVIDED "AS IS"  AND THE AUTHOR DISCLAIMS  ALL WARRANTIES WITH
REGARD TO THIS SOFTWARE INCLUDING  ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS.  IN NO  EVENT  SHALL THE  AUTHOR  BE LIABLE  FOR  ANY SPECIAL,  DIRECT,
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
OF USE, DATA OR  PROFITS, WHETHER IN AN ACTION OF  CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS ACTION, ARISING OUT OF OR IN  CONNECTION WITH THE USE OR PERFORMANCE OF
THIS SOFTWARE.