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

kzink

v1.0.4

Published

The mother of all unsorted kitchen sink js snippet collections. Built, maintaned and countinously added to by the developers at schjarven.no. Not at all meant to be of use or even comprehensible to anyone outside of our team.

Downloads

3

Readme

kzink

kzink!

The mother of all unsorted kitchen sink js snippet collections. Built, maintaned and countinously added to by the developers at schjarven.no. Not at all meant to be of use or even comprehensible to anyone outside of our team.

Rules

  • Maintain a folder structure that allows for require statements following the norm require('kzink/string/tokenize').
  • Submodules may contain its own submodules. These must be placed in a lib directory.
  • Sudmodules may (and should) contain a test.js file that runs with mocha and chai in TDD assertion style.
  • No dependencies allowed in package.json. Submodules may in certain circumstances require dependencies. These should not follow the installation of kzink, but rather the project that depends on that particular submodule of kzink.
  • In cases where a submodule is extracted from a project for inclusion in kzink, project-specific code must be generalized or removed. I.e. validate.maxlength_300(formvalue) should become validate.length(formvalue, min, max)

Updating

```$ ./update.sh ``