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

v0.1.5

Published

Produces JavaScripts files from template.

Downloads

2

Readme

grunt-jslocator

Produces custom JavaScript files containing the JavaScript file template modified with replaced texts on the languages previously set. This is useful for websites having more than one languages and have to display dialogs or specific messages on the chosen language.

Built with Grunt

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

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

grunt.loadNpmTasks('grunt-jslocator');

The "jslocator" task

Overview

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

grunt.initConfig({
  jslocator: {
    default_options:{
      options: {
          // Task-specific options go here.
          fileName: 'myDefaultLocalJS',
          source: 'test/fixtures/source.json',
          template: 'test/fixtures/template.js',
          open_varMark: '<%=',
          close_varMark: '%>'
      }
    }
  }
});

Options

options.fileName

Type: String Default value: 'myDefaultLocalJS'

A string value that is used to do something with whatever.

options.source

Type: JSON Default value: 'test/fixtures/source.json'

A file containing JSON formated data.

options.template

Type: String Default value: 'test/fixtures/template.js'

A file containing the js template with variables.

options.open_varMark

Type: String Default value: '<%='

Mark to denote variables to be replaced with data from source file. This goes at the beggining of the text to be replaced. You can use another mark of your preference.

options.close_varMark

Type: String Default value: '%>'

Mark to denote variables to be replaced with data from source file. This goes at the end of the text to be replaced. You can use another mark of your preference.

Usage Examples

Default Options

In this example, the pluging will produce two JavaScripts: myDefaultLocalJS.en.js and myDefaultLocalJS.fr.js. Each file contains the template from the file template.js but the variables teplaced with correspondent value stored on the source file source.json. Theses variables can be easy identified because they are surrounded by the open and close marks.

grunt.initConfig({
  jslocator: {
    default_options:{
      options: {
          fileName: 'myDefaultLocalJS',
          source: 'test/fixtures/source.json',
          template: 'test/fixtures/template.js',
          open_varMark: '<%=',
          close_varMark: '%>'
      }
    }
  }
});

Source file (JSON format) source.json

{
  "locales": ["en", "fr"]
  ,"vars":{
    "param1":{
      "en": "param #1"
      ,"fr": "1r parametre"
    }
    ,"param2":{
      "en": "param #2"
      ,"fr": "2e parametre"
    }
    ,"param3":{
      "en": "param #3"
      ,"fr": "3e parametre"
    }
  }
}

Template file (JavaScript format) template.js

/*
  TEMPLATE
*/
function foo(param1, param2){
  var msg = "";

  if (!isNaN(param1)){
    msg += "param1 <%=param1%>";
  }

  if (!isNaN(param2)){
    msg += "param2 <%=param2%>";
  }

  alert(msg + "<%=param3%>");

  return;
}

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

  • 2015-02-19   v0.1.0   Initial release.

License

Copyright (c) 2015 Dago Flores. Licensed under the MIT license.