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 🙏

© 2025 – Pkg Stats / Ryan Hefner

toxic-utils

v0.4.3

Published

utils

Downloads

361

Readme

toxic-utils

Build Status Coverage Status npm dependency Status devDependency Status Greenkeeper badge

utils collection

get started

npm install toxic-utils --save

if you are using flow, you should import our flow defination, by adding this to your .flowconfig.

[ignore]

[include]

[libs]
./node_modules/toxic-utils/lib/index.flow.js
[options]

[lints]

doc

genTraversalHandler

src/index.js:8-20

the handler to generate an deep traversal handler

Parameters

  • fn Function the function you wanna run when you reach in the deep property

Returns Function the handler

deepClone

src/index.js:27-32

deeply clone an object

Parameters

  • source (Array | Object) if you pass in other type, it will throw an error

Returns clone-target the new Object

deepAssign

src/index.js:38-50

merge multiple objects

Parameters

Returns merge-object [description]

camelize

src/index.js:57-63

camelize any string, e.g hello world -> helloWorld

Parameters

Returns string camelize string

hypenate

src/index.js:69-71

hypenate any string e.g hello world -> hello-world

Parameters

Returns string

bind

src/index.js:78-90

bind the function with some context. we have some fallback strategy here

Parameters

  • fn function the function which we need to bind the context on
  • context any the context object

Returns Function

uuid

src/index.js:95-97

generate an uuid

Returns string

S4

src/index.js:101-103

generate an random number which length is 4

Returns string

rand

src/index.js:108-114

generate an random number with specific length

Parameters

Returns string

getDeepProperty

src/index.js:119-147

get an deep property

Parameters

  • obj any
  • keys (string | Array<string>)
  • $2 any (optional, default {})
    • $2.throwError (optional, default false)
    • $2.backup