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

lodash-extensions

v0.0.1

Published

Lodash Extensions

Readme

lodash-extensions

Build Status Dependency Status devDependency Status

A library of extensions for lodash.js.

Installation

This package can be installed via bower:

bower install lodash-extensions

Installing dependencies

Install node.js and node package manager (npm).

From Debian and Ubuntu based distributions, use the following commands:

sudo apt-get install nodejs
sudo apt-get install nodejs-legacy
sudo apt-get install npm

For other distributions, you will not need the nodejs-legacy package. For information about other distributions, see: Installing node.js via package manager

Install Grunt Client (Optional)

To use the grunt-cli, it is easiest if it is installed globally.

sudo npm install -g grunt-cli

If you do not wish to install the grunt-cli, a script (see grunt file in project root) has been included. This allows you to use the local grunt-cli installation to run grunt commands. To do so, replace grunt in all grunt commands with ./grunt.

e.g. grunt becomes ./grunt, grunt build becomes ./grunt build

Install Project Specific Dependencies

This project has two kinds of dependencies: tools and libraries.

Tools:

  • are for managing and testing the application
  • are specified in package.json.
  • are installed via npm, the node package manager.

Libraries:

  • are the client-side dependencies which actually get shipped with the app.
  • are specified in bower.json.
  • are installed via bower, a client-side code package manager.

In this project, npm install has been configured to automatically run bower install, so we can simply run:

npm install

This will create the following folders:

  • node_modules - contains the npm packages for tools needed.
  • app/bower_components - contains bower packages for libraries needed.

Testing

Unit Tests

Unit tests are written in Jasmine 2.0, and run with the Karma Test Runner. We provide a Karma configuration file to run them.

  • Configuration for karma is found in karma.conf.js
  • Unit tests are to be named as follows: *.spec.coffee

Grunt tasks

Note: if using local grunt (described above), replace grunt in all commands listed below with ./grunt.

e.g. grunt build becomes ./grunt build

grunt build

This tasks compiles Coffeescript source files to Javascript in the build directory. It watches those files for changes, and re-compiles them on change.

This is the default grunt task.

Command: grunt or grunt build.

This task also gives you the option of running unit tests and compiling Coffeescript source files simultaneously. Tests will automatically re-run in response to changes in the source code / specs.

Command: grunt --test or grunt build --test

grunt test

This tasks compiles Coffeescript source files to Javascript in the build directory, and runs a single run of unit tests, outputing the test results to the console. Changes to files are not watched and the task terminates as soon as the unit tests complete.

Command: grunt test