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 🙏

© 2026 – Pkg Stats / Ryan Hefner

eslint-config-clock

v1.2.0

Published

Clock JavaScript Coding Standard

Readme

Clock JavaScript Coding Standard

This is an extension of standard minus the comma first and multi vars. We'd have loved to stick with standard 100% but we have a lot of active legacy projects and with this minor change we were able to easily nick all the good stuff that standard have defined.

Usage

In your project folder:

npm install --save-dev [email protected]
npm install --save-dev eslint-config-clock
npm install --save-dev [email protected]
npm install --save-dev [email protected]

Then create a .eslintrc in the project root.

{
  "extends": "clock"
}

Any override to the standards should go in this file.

Legacy Updates

The following can be used to fix some inconsistencies from our jshint/jscs projects.

First you need to install replace

npm install -g replace

replace 'function\(' 'function (' . -r --include='*.js' --exclude='node_modules,vendor'
replace 'function\s([^\s]+?)\(' 'function $1 (' . -r --include='*.js' --exclude='node_modules,vendor'
replace '\(\s([^ ])' '($1' . -r --include='*.js' --exclude='node_modules,vendor'
replace '([^\s\n])\s+\)' '$1)' . -r --include='*.js' --exclude='node_modules,vendor'
replace 'jshint camelcase: false' 'eslint camelcase: [2, {properties: "never"}]' . -r --include='*.js' --exclude='node_modules,vendor'
 
replace '=\s\s+(.)' '= $1' . -m false -r --include='*.js' --exclude='node_modules,vendor'

/function\s([^\s]+?)(/ to function $1 (

') )'' to '))'

'function(' to 'function (''

'( ' to '('

',function' to ', function'

/* jshint maxcomplexity: (\d+) / to / eslint complexity: [ 2, $1 ] */