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-coffee-strip-code

v0.1.3

Published

A Grunt task to remove develop and test only code blocks from CoffeeScript files for production build.

Downloads

9

Readme

grunt-coffee-strip-code Build Status

A Grunt task to remove develop and test only code blocks from CoffeeScript files for production build.

Getting started

Requirements: Grunt ~0.4.1 or above

Install in your workspace project

$ cd ~/your/workspace/project
$ npm install grunt-coffee-strip-code --save-dev

then add line to Gruntfile.js:

grunt.loadNpmTasks('grunt-coffee-strip-code');

The "coffee_strip_code" task

Overview

In Gruntfile.js add section named coffee_strip_code to the data object passed into grunt.initConfig().

grunt.initConfig({
  coffee_strip_code: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Task-specific file lists and/or options go here.
    },
  },
})

Options

options.start_comment_tag

Type: String

Default value: test-block-start

The text inside the opening comment used to identify code to strip.

options.end_comment_tag

Type: String

Default value: test-block-end

The text inside the closing comment used to identify code to strip.

options.pattern

Type: RegExp Default value: (a generated RegExp matching the start and end comments)

If the default start and end comment matching doesn't work for your needs, you can supply your own RegExp to match against. If the pattern option is specified, the start_comment and end_comment options are ignored.

Example Usage

The following source code exposes the bar function to the public API for testing, but the bar function should not be accessible in the released library. grunt-coffee-strip-code (with the default options) will remove the comment blocks from the example below keeping the bar function private in production:

( () ->

  bar = () ->
    doSomething()

  api = {
    foo: () ->
      bar()
    }
  }

  ## test-block-start ##
  api._bar = bar;
  ## test-block-end ##

  return api;
)()

Setting custom start/end comment tag

The following configuration will strip out code that begins with the /* start-test-block / comment and ends with the / end-test-block */ comment from all .js files in the dist/ folder.

grunt.initConfig({
  coffee_strip_code: {
    options: {
      start_comment_tag: 'test-block-start',
      end_comment_tag: 'test-block-end',
    },
    src: 'dist/*.coffee'
  },
})

Customize own pattern

The following configuration will remove log() statements from all .js files in the dist/ folder

grunt.initConfig({
  coffee_strip_code: {
    options: {
      pattern: /log\(\)/g
    },
    src: 'dist/*.coffee'
  },
})

Specifying source and destination.

The normal behavior is to strip out code in the source files and then save those files with the same name. If you need to save them to a different name, you can specify a dest option as well.

grunt.initConfig({
  coffee_strip_code: {
    options: { },
    files: [
      {src: 'tmp/my-app.coffee', dest: 'dist/my-app.coffee'},
      {src: 'tmp/my-lib.coffee', dest: 'dist/my-lib.coffee'},
    ],
  },
})

Contribute

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.3 Added travis watcher
  • 0.1.2 Fixed few typos into documentation
  • 0.1.1 Fixed few typos into documentation
  • 0.1.0 Initial release

License

The MIT License (MIT)

Copyright (c) 2014 Maciej Sypień

This Project was inspired by Philip Walton and his grunt-strip-code package.