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-commandl10n

v0.0.2

Published

Identifies unused localization key/value pairs in a project

Readme

grunt-commandL10n

NOTE: currently in development. working thru some things

Identifies unused localization key/value pairs in a project. Recursively reads the directory and its sub-directories, comparing localization string variables from the view with the locale file(ie en.json) key/value pairs

Install the package - "grunt-commandl10n"

npm install grunt-commandl10n --save-dev

Load the task - "grunt-commandl10n"

grunt.loadNpmTasks('grunt-commandl10n');

Register the task - "commandL10n"

grunt.registerTask('L10n', ['commandL10n:files']);

Update the config settings

In your project's Gruntfile, add a section named commandL10n to the data object passed into your config settings, grunt.initConfig().

grunt.initConfig({
    commandL10n: {
	files: {
	    localization: {
		path: 'path/to/your/locale/folder/en.json'
	    },
	    view: {
		path: 'path/to/your/view/folder/to/read'
	    }
	},
	options: {
	    write:{
		path: 'path/to/your/locale/folder/enSoFreshSoClean.json'  // optional
	    }
	}
    }
})

More Information

You do have to set the path to your localization file (ie en.json, es.json en-au.json) and the path to your view folder in the connfiguration.

Unless you want the resulting cleaned up json to be written to a new file or folder, don't worry about the options object in the configuration.

Running from the command line

npm install and link
	> npm link
command line example
	> grunt L10n

Running Tests unit test(server)

Using mocha, sinon and chai for unit testing server

In command line:
mocha test/unit/server/grunt-commandL10nSpec --reporter spec

License

Copyright (c) 2015 Norman Barber. Licensed under the MIT license.