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

v0.2.1

Published

Grunt plugin to preprocess HTML, JavaScript, CSS, XML, etc.

Downloads

8

Readme

grunt-clopp

clopp is a cross-language omni-functional preprocessor designed to make building for multiple targets easy

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

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

grunt.loadNpmTasks('grunt-clopp');

clopp

Introduction

clopp is a tool that you can add to your toolchain which will allow you to do certain things at compile time of your project. It is designed to be run in a fully fledged production environment.

Why would you want to do things at compile time with JavaScript?

Valid question. There are several use-cases for this kind of thing:

  1. If you have multiple build targets (i.e. a production environment, staging environment, dev environment), you can easily use specific pieces of code per build target.
  2. If you want to disable pieces of code while developing, but want them actived when your app gets compiled, clopp can do that for you.
  3. If you have large chunks of text that you do not want in your development files, but do need in your files when it's compiled, you can easily include a file & clopp does the trick!
  4. If you have any experience with other preprocessors (such as the one in C++), you will understand how useful macros (or other definitions) are.
  5. You can clopp it like it's hot... hehehehe

What languages does clopp support?

  1. JavaScript
  2. TypeScript
  3. HTML (and JavaScript inside HTML, obviously!)
  4. CSS / LESS / SASS
  5. C / C# / C++
  6. Java
  7. PHP

Here is a short example of what clopp can do for you.

// #define fooFactor 3

// #ifdef fooFactor
function Foo(a, b)
{
    return a + b * fooFactor;
}
// #endif

Turns into this at compile time:

function Foo(a, b)
{
    return a + b * 3;
}

Configuring clopp

Configuring your files that need to be preprocessed

clopp, as of now, "only" supports the standard Grunt files configuration. We recommend you use the files array format, but also support the object format and the compact format. There is one catch though. The destination needs to be a folder that already exists if you decide to omit inline preprocessing. If you choose to do inline preprocessing (which is further explained down below), clopp will omit your destination folder. It is in the to-do list to have this fixed, luckily.

Here is an example of a basic configuration of clopp using the array format:

grunt.initConfig({
    clopp: 
    {
        preprocess: 
        {
            files:
            [
                { src: 'sourceFile.js', dest: '/destination/' }
            ]
        }
    }
});

Configuring options for the preprocessor

You can configure a lot of options in the preprocessor. Here's the ones that you can define:

options.inline

Type: boolean Default value: false

This is probably the most controversial option you can enable. If you set this to true, the preprocessing will happen in your source files. This is potentionally very dangerous. It can cause severe code loss in your projects if you don't take the right safety precautions.

If you set this to true, you do not have to configure any destination folder anymore.

options.context

Type: object Default value: {} (empty object)

This is an option that you will probably need in your configuration. It allows you to set the context in which the preprocessor operates. It's an object which contains #defines that clopp will use as if you used the #define statement in your source code. Sorry if that explanation is a bit weird, but please try understand this example configuration of options.context:

grunt.initConfig({
    clopp: 
    {
        preprocess: 
        {
            options: {
                context: {
                    myDefinition: "myValue",
                }
            },
            files:
            [
                { src: 'sourceFile.js', dest: '/destination/' }
            ]
        }
    }
});

options.definitions

Type: boolean Default value: true

If you set this to false, clopp will no longer look for any #define statements in your code.

options.include

Type: boolean Default value: true

If you set this to false, clopp will no longer look for any #include statements in your code.

options.exclude

Type: boolean Default value: true

If you set this to false, clopp will no longer look for any #exclude statements in your code.

options.skips

Type: boolean Default value: true

If you set this to false, clopp will no longer look for any #skip statements in your code.

options.preprocess

Type: boolean Default value: true

If you set this to false, clopp will no longer look for any #if, #ifdef or #ifndef statements in your code.

options.filetypes

Type: boolean Default value: false

This enables or disables the #filetype statements in your code.

clopp syntax

#filetype

#filetype allows you to override the type that clopp finds for your files (which is originally determined by extracting the extension from the file name).

Examples of #filetype in JavaScript:

// #filetype JavaScript
/* #filetype JavaScript */

List of supported keywords for #filetype (non case-sensitive):

  1. JavaScript: JavaScript and JS
  2. TypeScript: TypeScript and TS
  3. CSS: CSS, SASS and LESS
  4. HTML: HTML
  5. XML: XML
  6. C / C# / C++: C, C#, C sharp, Csharp, C-sharp, C++, cpp, cc
  7. Java: Java
  8. PHP: PHP

#define

#define is a statement you can put in your code which clopp will pick up. It basically works like a JavaScript variable. clopp will do a text based search & replace on all your files and replace all definitions it can find with the definitions' value.

Examples of #define in JavaScript:

// #define myDefinition 10
/* #define myOtherDefinition 11 */
// #define myMacro (function(text){console.log(text);})

Quick note: definition names & definition values cannot hold any spaces

#include

#include is a statement you can put in your code which clopp will pick up. You can use to include another file at the point where you call your #include.

Examples of #include in JavaScript:

// #include myInclude.txt
/* #include myOtherInclude.txt */
// #include includes/anotherInclude.js

#exclude

#exclude is a statement you can put in your code which clopp will pick up. You can use to exclude specific pieces of code from your file. Please note that #exclude requires an end statement, which is #endexclude.

Examples of #exclude in JavaScript:

// #exclude
console.log("This code will not be here anymore when it's passed compile time!");
// #endexclude

console.log("This code will be here after compile time!");

/* #exclude */
console.log("This code will also not be here anymore when it's passed compile time!");
/* #endexclude */

#skip

#skip is a statement you can put in your code which clopp will pick up. You can use #skip to skip the current file and not preprocess it at all. That effect happens when your #skip statement is found anywhere in the file, even if it is at the very bottom of your file.

Examples of #skip in JavaScript:

// #skip
/* #skip */

#ifdef

#ifdef is a statement you can put in your code which clopp will pick up. You can use #ifdef when you want to check if a given definition is already defined or not.

Examples of #ifdef in JavaScript:

// #ifdef myDefinition
console.log("Cool! myDefinition is defined!");
// #endif

/* #ifdef myOtherDefinition */
console.log("Cool! myOtherDefinition is also defined!");
/* #endif */

#ifndef

#ifndef is a statement you can put in your code which clopp will pick up. You can use #ifndef when you want to check if a given definition is not defined.

Examples of #ifndef in JavaScript:

// #ifndef myDefinition
console.log("Cool! myDefinition is not defined!");
// #endif

/* #ifndef myOtherDefinition */
console.log("Cool! myOtherDefinition is also not defined!");
/* #endif */

#if

#if is a statement you can put in your code which clopp will pick up. #if is a rather complicated statement in clopp, though. I will not fully explain it here, but supply you with more examples further down the page.

#if allows you to write conditions as you would like. Your actual condition actually gets executed in actual JavaScript, so when you write #if statements, make sure you write as if you are writing actual JavaScript.

Examples of #if in JavaScript:

// #if 1+1==2
console.log("Today I learned that 1+1 equals 2.");
// #endif

/* #if 2+2==4 */
console.log("WOW! Even more we learned today, 2+2 equals 4!");
/* #endif */

// Here is a neat little trick! This trick will work with all multiline statements in clopp :)

// This trick will allow you to have code disabled while you are developing it, but depending on whether or not
// your condition passes at compile time clopp enables / disables it. If you are confused, try it out yourself!

// The trick here, is that I am omitting the "*/" at the end of my #if statement. This will disable the code while developing it.

/* #if 3+3==6
console.log("Apparently, 3+3 equals 6!");
/* #endif */

#elseif

#elseif is a statement you can put in your code which clopp will pick up. #elseif functions pretty much in the same way as any #if statement would function, however it has to be inside an #if block. It's on the to-do list to loosen up this syntax (because it is very strict at the moment), however if-elseif-else logic is really complicated when you are in the world of regex. Sorry!

Examples of #elseif in JavaScript:

// #if 1+1==3
console.log("Today I learned that 1+1 equals 3.");
// #elseif 1+1==4
console.log("Okay, what dimension are we in where 1+1 equals 4?");
// #elseif 1+1==2
console.log("Back on earth! 1+1 does equal 2!");
// #endif

#else

#else is a statement you can put in your code which clopp will pick up. #else functions in cohesion with #if and #elseif. It is a very straight forward block of code, however it has to be inside an #if block, just like #elseif.

Examples of #else in JavaScript:

// #if 1+1==3
console.log("Today I learned that 1+1 equals 3.");
// #else
console.log("Okay, okay.. 1+1 does not actually equal 3..");
// #endif

// And an example of how to use it in cohesion with an #if & #elseif statement

// #if 1+1==3
console.log("Today I learned that 1+1 equals 3.");
// #elseif 1+1==4
console.log("Okay, what dimension are we in where 1+1 equals 4?");
// #else
console.log("Hrrm.. okay we don't know what 1+1 equals to!");
// #endif