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-msg-init-merge

v0.0.5

Published

Grunt task for msginit and msgmerge

Downloads

50

Readme

grunt-msg-init-merge

Grunt task for msginit and msgmerge

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-msg-init-merge --save-dev

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

grunt.loadNpmTasks('grunt-msg-init-merge');

The "msgInitMerge" task

Overview

This task runs for each locale:

  • msginit if .po file does not exist to create it.
  • msgmerge if .po file exists to update it with new keywords.

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

grunt.initConfig({
  msgInitMerge: {
    your_target: {
      src: ['test/fixtures/myDomain.pot'],
      options: {
          locales: [{name: 'ru_RU', folder: 'ru'}, 'en'],
          poFilesPath: 'tmp/i18n/<%= locale%>/<%= potFileName%>.po',
      }
    }
  },
});

You should specify:

  • locales - list of locales
  • poFilesPath - template for *.po files location.
  • src - location of *.pot files.

Task in example above will create/update *.po files:

  • tmp/i18n/ru/myDomain.po
  • tmp/i18n/en/myDomain.po

Specifying target (e.g. "your target") is necessary!

Options

options.locales

Type: Array

Default value: []

List of locales, e.g.:

[{name: 'ru_RU', folder: 'ru'}, 'en']

If locale is an Object:

  • name - will be passed to msginit --locale=name
  • folder - will be used as locale variable in poFilesPath template (folder name).

options.poFilesPath

Type: String

Default value: ''

Template for *.po files location, e.g.:

tmp/i18n/<%= locale%>/<%= potFileName%>.po

Available variables:

  • locale - locale folder
  • potFileName - name of a *.pot file
  • potDirName - dir path of a *.pot file

options.msgInit

Type: Object

Default value:

msgInit : {
    cmd : 'msginit',
    opts : {}
}

You can specify path to msginit or additional options:

msgInit : {
    cmd : '/opt/local/bin/msginit',
    opts : {
        width : 50
    }
}

The 'cmd' property must be present if you decide to specify additional options

options.msgMerge

Type: Object

Default value:

msgMerge : {
    cmd : 'msgmerge',
    opts : {}
}

You can specify path to msgmerge or additional options:

msgMerge : {
    cmd : '/opt/local/bin/msgmerge',
    opts : {
        width : 50
    }
}

The 'cmd' property must be present if you decide to specify additional options