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-qpoc-closure-compiler

v0.1.2

Published

Extended closure compiler plugin with module support.

Downloads

18

Readme

UNDER DEVELOPMENT

grunt-qpoc-closure-compiler

Extended closure compiler plugin with module support.

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-qpoc-closure-compiler --save-dev

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

grunt.loadNpmTasks('grunt-qpoc-closure-compiler');

The "qpoc_closure_compiler" task

Overview

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

grunt.initConfig({
  qpoc_closure_compiler: {
    your_mode: {
      options: {
        // Task-specific options go here.

        // path to compiler.jar of google closure compiler
        // default: environment variable CLOSURE_COMPILER
        closureCompiler: './compiler.jar',

        // path to the closure library folder which contains "closure",
        // "third_party" ...
        // default: environment variable CLOSURE_LIBRARY
        closureLibrary: '/closure-library/',

        // Java executable path
        // default: 'java'
        javaPath: 'java',

        // whether automaticaly add the closure library to the pathes
        includeClosureLibrary: true, // default: true

        workspaces: [
          {
            // paths to libraries which are required in your application
            path: './lib/'
          }
          // ... further ones
        ],


        // defines the way you want to split your application
        modules: [
          // define your main module at the start
          // it's required to define one main module which will be the
          // dependency of all further modules
          {
            // path to the initiate script of the module
            path: './lib/init.js',

            // name of the module
            name: 'app'
          },

          {
            path: './lib/the_mod.js',
            name: 'the_mod',
            // array of modules which are required
            dependencies: ['app']
          }
        ],

        level: {
          advanced: true // default is false
        },

        // formatting of the code exported by the compiler
        prettyPrint: false, // default is true

        // path for the generated files
        // default: ./tmp/
        outputDir: '.',

        // prefix for the exported module javascript files.
        // example: module name "app", prefix: "module_"
        // => "#{ outputDir }/module_app.js"
        modulePrefix: '',

        // automaticaly exports a module.js.map into the outputDir
        sourceMaps: true // default: false
      }
    }
  },
})

Options

options.closureCompiler

Type: String Default value: environment $CLOSURE_COMPILER

Description following...

To be continued... Please look at the example above

Release History

(Nothing yet)