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-pre-proc

v2.0.0

Published

The super simple preprocessor for front-end development.

Downloads

2

Readme

grunt-pre-proc

npm GitHub issues David license

This Grunt plugin is wrapper of preProc.

The super simple preprocessor for front-end development.
See preProc for options and more information about preProc.

Getting Started

This plugin requires Grunt ~0.4.1

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-pre-proc --save-dev

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

grunt.loadNpmTasks('grunt-pre-proc');

Usage

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

grunt.initConfig({
  preProc: {
    deploy: {
      options: {
        // Remove `DEBUG` contents from all files in `dir1` directory and all JS files.
        removeTag: {tag: 'DEBUG', pathTest: ['/path/to/dir1', /\.js$/]}
      },
      expand: true,
      cwd: 'develop/',
      src: '**/*',
      dest: 'public_html/'
    }
  }
});

Options

removeTag

If removeTag option is specified, call removeTag method with current content.

You can specify an object that has properties as arguments of the method.
Following properties are accepted:

  • tag
  • pathTest

Also, you can specify common values for the arguments into upper layer. That is, the options.pathTest is used when options.removeTag.pathTest is not specified.

If the pathTest is specified, current source file path is tested with the pathTest. If there are multiple source files (e.g. src: ['file1', 'file2'], src: '*.js', etc.), the first file path is tested.

For example:

grunt.initConfig({
  preProc: {
    deploy: {
      options: {
        tag: 'DEBUG',           // common
        pathTest: '/path/to',   // common

        removeTag: {},                            // tag: 'DEBUG', pathTest: '/path/to'
        replaceTag: {tag: ['SPEC1', 'SPEC2']},    // tag: ['SPEC1', 'SPEC2'], pathTest: '/path/to'
        pickTag: {}                               // tag: 'DEBUG', pathTest: '/path/to'
      },
      // ...
    }
  }
});

replaceTag

If replaceTag option is specified, call replaceTag method with current content.

You can specify arguments by the same way as the removeTag.
Following arguments are accepted:

  • tag
  • pathTest
  • replacement (As options.replaceTag.replacement, not options.replacement)

pickTag

If pickTag option is specified, call pickTag method with current content.

You can specify arguments by the same way as the removeTag.
Following arguments are accepted:

  • tag
  • allowErrors (As options.pickTag.allowErrors, not options.allowErrors)

When the tag was not found, this method throws an error by default. If true is specified for allowErrors, it returns null (not a string) without error. It is useful for handling unknown source code. (No file is saved.)
Also, you can specify options to call multiple methods, and other methods are not called when the tag was not found.