Package Exports

grunt-lokalise_co

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (grunt-lokalise_co) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

grunt-lokalise_co

lokalise.co grunt plugin.

Getting Started

This plugin requires Grunt.

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-lokalise_co --save-dev

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

grunt.loadNpmTasks('grunt-lokalise_co');

The "lokalise_co" task

Overview

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

grunt.initConfig({
  lokalise_co: {
    my_project: {
        options: {
            api_token: '', /* (required) */
            id: '', /* project id (required) */
            type: 'json', /* file format (po, xls, strings, xliff, xml, json, php, yml, properties, ini) (defaults to `json`) */
            langs: ['en', 'de'], /* list of languages to be exported. If omitted, all languages are exported */
        },
        dest: '.locales'
    }
  },
})

Test

npm test

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

0.1.0 initial release

License

See MIT