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

@airikleon/coffee-lint

v0.0.8

Published

Pseudo Coffeescript linter via Eslint

Readme

Coffeescript Linter

Required to work

Description

This is a simple linter that uses eslint to lint the javascript files produced by coffeescript.

The intention for this package is to remain a wrapper for simply mapping errors from coffeescript & eslint. All of the configuration is handled by an eslint config.

The package uses standard input for the files. The expectation here is that files are seperated by a newline \n

For example, and my personal use case, is I need to only lint the coffeescript files that are actually changed. So to do that we type the following command.

Using the Pipe (|) operator we can pass output into the next command.

git ls-files --exclude="node_modules/" -m -o | grep "**/*.coffee" | coffee-lint

This section produces a list of files excluding node_modules

git ls-files --exclude="node_modules" -m -o

This uses a glob pattern to only grab coffeescript files

 grep "**/*.coffee" 

This is the actual program taking in the piped input

coffee-lint

This package currently uses the stylish formatter for outputting errors, example below:


/var/lib/jenkins/workspace/Releases/eslint Release/eslint/fullOfProblems.js
  1:10  error    'addOne' is defined but never used            no-unused-vars
  2:9   error    Use the isNaN function to compare with NaN    use-isnan
  3:16  error    Unexpected space before unary operator '++'   space-unary-ops
  3:20  warning  Missing semicolon                             semi
  4:12  warning  Unnecessary 'else' after 'return'             no-else-return
  5:1   warning  Expected indentation of 8 spaces but found 6  indent
  5:7   error    Function 'addOne' expected a return value     consistent-return
  5:13  warning  Missing semicolon                             semi
  7:2   error    Unnecessary semicolon                         no-extra-semi

✖ 9 problems (5 errors, 4 warnings)
  2 errors and 4 warnings potentially fixable with the `--fix` option.

For source code or PR(s) visit repo here