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

v0.2.1

Published

Validate files with Google Closure Linter.

Downloads

849

Readme

grunt-gjslint

Validate files with Google Linter.

Getting Started

This plugin requires Node ~0.8.19 (for managing peerDependencies), Grunt ~0.4.1 and just python2 installed.

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

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

grunt.loadNpmTasks('grunt-gjslint');

The gjslint and fixjsstyle tasks

Run this tasks with the grunt gjslint or grunt fixjsstyle commands.

Overview

In your project's Gruntfile, add sections named gjslint and fixjsstyle to the data object passed into grunt.initConfig(). Some of the flags passed to gjslint don't work with fixjsstyle.

grunt.initConfig({
  gjslint: {
    options: {
      flags: [
        '--disable 220', //ignore error code 220 from gjslint,
        '--flagfile .gjslintrc' //use flag file
      ],
      reporter: {
        name: 'console' //report to console
      },
      force: false, //don't fail if python is not installed on the computer. Default: `true` 
      pythonPath: '/your/path/to/python2' //closure-linter only works with python2. Specify the path to it. Default: `python` 
    },
    lib: {  //specify your targets, grunt style.
      src: ['lib/module/**/*.js', 'lib/foo.js'],
    },
    test: {
      src: '<%= jshint.test %>',
    }
  },
  fixjsstyle: {
    options: {
      flags: [
        '--disable 220' //ignore error code 220 from gjslint
      ],
      reporter: {
        name: 'console'
      }
    },
    all: {
      src: '<%= jshint.all %>'
    }
  }
})

As this is a Multitask, you can specify several targets to be called sharing the same root options

Documentation

grunt-gjslint uses node-closure-linter-wrapper to lint files

Please, refer to node-closure-linter-wrapper documentation for flags, reporter and pythonPath reference.

options.force flag is a custom option that when disabled, will not fail the grunt task when python is not installed on the computer. It defaults to true

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Lint and test your code using Grunt.

Release History

  • v0.1.6: Huge amount of files in windows support. @ganxiyun
  • v0.1.5: added fixjsstyle task
  • v0.1.4: bug fixing in filenames with whitespaces. Thanks to @moelders
  • v0.1.3: bug fixing. Thanks to @dcantelar
  • v0.1.0: First version