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

grunt-custom-coffee

v0.0.1

Published

Compile CoffeeScript files to JavaScript -- you bring the compiler!

Readme

grunt-custom-coffee

Build Status Dependency Status

Compile CoffeeScript files to JavaScript -- you bring the compiler!

About

This plugin is a copy of grunt-contrib-coffee with one difference:

      return (options['compiler'] || require('coffee-script')).compile(code, options);

That line from the task file allows you to provide your own "CoffeeScript" compiler.

Most of the time, you would use this task to gain control of the version of CoffeeScript that is used to compile your .coffee or .litcoffee files. For instance, you may require a specific version, or you may require a customized compiler, such as the hleumas fork which has additional support for Google Closure Library. It doesn't really matter what you specify as your compiler as long as it does what you want when you call compile(code, options) on it. :)

Please see the grunt-contrib-coffee task for full documentation. The only difference here is that you may use the compiler option to override the default compiler:

compiler

Type: object Default: undefined

If provided, the compiler is expected to be an instance of the npm package 'coffee-script' or something that behaves as if it were. This can be used to build with an alternate version of coffee-script or to build with a fork of coffee-script. Typically, the user will specify the compiler using compiler: require('coffee-script') where an alternate version of coffee-script has been specified by the package as a direct dependency.

Release History

  • 2013-10-01   v0.0.1   Initial release -- equivalent to grunt-contrib-coffee v0.7.0.