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

@kingstinct/utils

v0.7.27

Published

⚠️ This repo has been moved to [Kingstinct/zemble](https://github.com/kingstinct/zemble/tree/main/packages/utils), and has been renamed to [`@zemble/utils`](https://www.npmjs.com/package/@zemble/utils).

Downloads

494

Readme

⚠️ This repo has been moved to Kingstinct/zemble, and has been renamed to @zemble/utils.

@kingstinct/utils

npm (scoped)

This is a generic utility library that we use across our projects at Kingstinct (still early days for this lib).

There are two main imports, one generic and one for some node-specific stuff: import { wait, times, sample, logPrettyData } from '@kingstinct/utils'

import { gravatarUrlForEmail } from '@kingstinct/utils/lib/node'

You can also import utilities directly: import wait from '@kingstinct/utils/lib/wait'

The goal of this library (and the related @kingstinct/react) is to:

  • Keep the number of dependencies in projects down
  • Have a common place to put useful utilities, so they're easier to maintain and find
  • Quickly get up and running with new projects

We believe this is a better approach than the alternatives:

  • Using one single utility library for everything, which would introduce unnecessary dependencies
  • Using lots of micro-libs. Micro-libs does have it's advantages, but is harder to maintain and means loosing oversight of the dependencies in a project.
  • Copy pasting between projects :)

Timeoutify

Timeoutify is a utility to handle timeouts making it easy to clean up resources when a timeout occurs, and it can also be aborted for other reasons (client disconnects for example).

The easiest way to use it is through the Fastify plugin, and access it on from your request object:

import fastify from 'fastify'
import { timeoutifyPlugin } from '@kingstinct/utils/fastify/timeoutifyPlugin'
import mongodb from 'mongodb'

const fastifyServer = fastify()
fastifyServer.register(timeoutifyPlugin, { timeoutMS: 30000 }) // <- time out your request after 30 seconds

const db = await mongodb.connect('mongodb://localhost:27017', { timeout: req.timeoutify.timeout })

fastifyServer.get('/callSomeOtherApi', async (req, res) => {    
  const result = await fetch('https://api.slow.app', { signal: req.timeoutify.abortSignal });
  return result;
})

fastifyServer.get('/callMongoDb', async (req, res) => {    
  const result = await req.timeoutify.runMongoOpWithTimeout(
    db.collection('users').find({})
  );
  return result;
})

This will take care of the following:

  • If the timeout (of 30s in this example) is hit a 504 response will be sent to the client.
  • If the client disconnects (ex: closes browser tab) a 499 response will be sent to the client.
  • If the request is aborted (by either a timeout or client disconnect) the fetch request will be aborted. Works with any calls supporting AbortSignal.
  • If the request times out the MongoDB query will time out at the same time. This ensures that MongoDB queries are not left hogging resources.