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 🙏

© 2024 – Pkg Stats / Ryan Hefner

grunt-bln-i18n

v1.0.0

Published

BLN i18n utilities.

Downloads

2

Readme

grunt-bln-i18n

Utility tasks for BLN i18n support

Getting Started

Install the plugin with this command:

npm install grunt-bln-i18n --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-bln-i18n');

An alternative way is to use a plugin loader like load-grunt-tasks.

i18n-extract-keys task

Extracts translation keys from application source.

Uses standard grunt multi-task configuration.

Sample configuration

'i18n-extract-keys': {
	options: {
		keyRegexp: /\b_t\s*\(\s*'(\w+)'([^)]*)?\)/g
	},
	all: {
		src: ['app/scripts/**/*.js', 'app/scripts/**/*.html'],
		dest: '.tmp/keys.json'
	}
}

src

Type: String|Array

Application source files. These files are searched for translation function calls.

dest

Type: String

The destination JSON files for storing encountered translation keys. The keys are stored as a sorted array without duplicates.

options.keyRegexp

Type: RegExp

Regular expression used to find calls to the translation function. The first parenthesized substring match is used as the resulting translation key.

i18n-check-keys task

Checks specified translation file content, with expected translation keys specified in format matching i18n-extract-keys task output.

Translation files checks:

  • must be parsable by the l20n library
  • must contain all the expected translation keys

Expected translation key file checks:

  • must be in correct format
  • must not contain any translation keys starting with an underscore (such keys are considered private & internal to each translation file and should not be directly used from application code)

Uses standard grunt multi-task configuration without a destination file.

Sample configuration

'i18n-check-keys': {
	all: {
		options: {
			keys: '.tmp/keys.json'
		},
		src: 'app/locales/*.l20n'
	}
}

src

Type: String|Array

Translation files. These files will be checked for validity and key presence. Every file will be parsed and compiled using the l20n library. If this step fails the task will be immediately aborted.

Afterwards, the files will be checked to make sure that they contain all the expected translation keys. Missing keys are will be logged. The task is marked as failed if any file has any missing keys.

options.keys

Type: String

A JSON file containing array of keys to search for in translation files.

Development

We use grunt as our task runner so make sure you have it installed globally for your node.

To lint the code and run tests use:

grunt test