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 🙏

© 2025 – Pkg Stats / Ryan Hefner

elgg-grunt

v0.4.0

Published

elgg-grunt ===================

Downloads

3

Readme

elgg-grunt

Shared grunt configuration for Elgg 2.0 plugins and sites.

Usage

1. Put this as your project's Gruntfile.js:

module.exports = require('elgg-grunt');

2. Add a profiles.local.json

Your local server needs to point to the /dist/ directory, which is where the built files will end up.

{
  "baseUrl": "http://localhost:8080/dist/"
}

3. Run grunt watch

Just grunt watch; no flags or subcommands.

This gives you the default local build, and automatically updates as you make changes. Load up the app at baseUrl to see it in action.

NB: You need to start the server yourself. How to do that is different based on each environment.

TODO(evan): Provide a default local server.

Releasing

This project and any project that relies on this one to provide its Gruntfile configuration can use the following commands to quickly push new versions to NPM.

# Bugfix releases (e.g. 1.0.x)
grunt release:patch
npm publish

# New feature releases (e.g. 1.x.0)
grunt release:minor
npm publish

# Backwards-incompatible releases (e.g. x.0.0)
grunt release:major
npm publish

Each of these will generate the appropriate changelog updates assuming you have been diligent to adhere to the recommended commit message format.

Continuous Testing

Add .travis.yml to your app:

language: node_js
node_js:
- '0.11'
script: grunt travis
branches:
  only:
  - master

Continuous Deployment

Travis-CI can push your app to gh-pages/staging/production every time all your tests pass. This example walks you through auto-pushing to GitHub pages:

Setup a gh-pages branch for deployment

You can follow the instructions here:

https://github.com/X1011/git-directory-deploy

Add a .travis.yml file

language: node_js
node_js:
- '0.11'
script: grunt travis
after_success: bin/deploy.sh gh-pages
branches:
  only:
  - master

Note that this also includes a after_success: bin/deploy.sh script. You need to copy deploy.sh from the ng-elgg repo until continuous deployment is supported out of the box.

Give Travis-CI your credentials

gem install travis
cd my_project
travis encrypt GITHUB_TOKEN=XXXXX --add

Replace XXXXX with your GitHub command line token for the repository.

Make sure Travis is running on commits to your repo