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

v1.1.0

Published

A Grunt task to run jsxgettext against files to extract strings into a POT file.

Downloads

10

Readme

grunt-jsxgettext

Build Status

A Grunt task to run jsxgettext extracting strings and creating POT files.

Example

grunt.initConfig({
  jsxgettext: {
    test: {
      files: [
        {
          src: ['tests/fixtures/**/*.*js', '!ignored'],
          output: 'test.po',
          'output-dir': './translations/'
        }
      ],
      options: {
        keyword: ['gettext']
      }
    }
  }
})

Options

**** generators

Type: 'String' or 'function' Default:

[
    {ext: '.ejs': generator: jsxgettext.generateFromEJS},
    {ext: '.hbs', generator: jsxgettext.generateFromHandlebars},
    {ext: '.jade', generator: jsxgettext.generateFromJade},
    {ext: '.swig', generator: jsxgettext.generateFromSwig} 
]

Used to add/modify mapping between file extensions and generators (parsers) used by jsxgettext.

This can be one of the following:

  • Specifying a pair of extensions. Used to add a extensions for existing generators. For example if we wanted to tell jsxgettext that our handlebars templates have '.html' extensions: {ext: '.html': generator: '.hbs'}
  • Specifying an extension along with the jsxgettext generator function name: {ext: '.html': generator: 'generateFromSwig'}
  • Specifying an extension along with an generator function: {ext: '.html': generator: jsxgettext.generateFromSwig}

Getting Started

This plugin requires Grunt ~0.4.2

npm install grunt-jsxgettext --save-dev

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

grunt.loadNpmTasks('grunt-jsxgettext');