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-simple-text

v1.3.3

Published

Replace text with a key value from a json file

Downloads

23

Readme

grunt-simple-text

Replace text with a key value from a json file

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-simple-text --save-dev

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

grunt.loadNpmTasks('grunt-simple-text');

The "simple_text" task

Overview

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

grunt.initConfig({
  simple_text: {
    options: {
      json: ['path/to/file.json', 'path/to/another.json'],
      key: 'default',
      defaultKey: 'default',
      openBracket : '{',
      closeBracket : '}'
    },
    your_target: {
      files : {
        "path/save/file.html" : "path/process/file.html"
      }
    },
  },
});

Options

options.json

Type: String|Array Default value: ''

Path to a single json file or construct array of multiple json files containing the strings that can be added to your files.

options.key

Type: String Default value: 'default'

Key in json has multiple text sources for the same text identifiers. This can come in handy if using different text for different release platforms.

options.defaultKey

Type: String Default value: ''

To save creating multiple keys where the value is the same for multiple environments, specify a default key and the key value will override where necessary.

options.openBracket

Type: String Default value: '{'

Open bracket symbol to identify the key name to get the string value.

options.closeBracket

Type: String Default value: '}'

Close bracket symbol to identify the key name to get the string value.

Usage Examples

Custom Options

This example will take the file.html and check for any strings between {}, these will be used as keys to get any values from the parent key 'Default' in the file.json.

grunt.initConfig({
  simple_text: {
    main : {
      options: {
        json: 'path/to/file.json',
        key: 'release',
        defaultKey: 'default',
        openBracket : '{',
        closeBracket : '}'
      },
      files: {
        'dest/output.html': ['src/orig/file.html'],
      }
    }
  }
});

If file.html has the contents

<div class="textItem">
  <p>{LongText}</p>
</div>

and file.json has the contents

{
  "default" : {
    "LongText" : "Lorem ipsum dolor sit amet, consectetur adipiscing elit."
  },
  "release" : {
    "LongText" : "Actual long text for release."
  }
}

then output.html will save with

<div class="textItem">
  <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit.</p>
</div>

If the key option had been set to release, the output.html file would have this as it's contents

<div class="textItem">
  <p>Actual long text for release.</p>
</div>

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.