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

@flekschas/utils

v0.32.2

Published

A set of utility functions I use across projects

Downloads

2,127

Readme

A collection of handy utility functions

NPM Version Build Status File Size Code Style Prettier Docs

This is a collection of utility functions that I keep using across different projects. I primarily created this package for myself so I don't have to re-implement certain functions over and over again, and to have a central place for testing them.

Install

npm install @flekschas/utils --save-dev

Usage

import { debounce } from '@flekschas/utils';

const hi = debounce(() => {
  console.log('I am debounced');
}, 250);

For cherry picking from a specific topic do:

import { debounce } from '@flekschas/utils/timing';

The utility functions are organized by the following topics:

  • animation
  • color
  • conversion
  • dom
  • event
  • functional-programming
  • geometry
  • map
  • math
  • object
  • other
  • sorting
  • string
  • timing
  • type-checking
  • vector

API

See API.md for the API docs.

Why yet another library for utility functions?

Generally, I follow four core goals with this collection:

  1. Reusability
  2. Performance
  3. Simplicity
  4. No dependencies

Whenever a function is reusable in a general context I might add it. When I add a function I will make sure it's performant. Finally, every function should be implement as simple as possible without harming performance. There's always a trade-off between performance and simplicity and my philosophy is the following: if the simple and complex implementation perform roughly the same, I choose the simple implementation. If a slightly more complex implementation is much faster I will favor the complex implementation. In any case, the API should always be simple and easy to understand! Finally, I want my utils functions to have no external and as little as possible internal dependencies. Why? No matter how large this collection becomes as a whole, if you only need one function, you should only ever have to bundle a single function and not a whole forrest of depending helper functions.