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

quick-grunt-config-coding-conventions

v0.1.1

Published

Module containing a generator for configurations for Grunt tasks for coding-conventions checks.

Downloads

9

Readme

quick-grunt-config-coding-conventions

Module containing a generator for configurations for Grunt tasks for coding-conventions checks.

NPM version Dependency Status Development Dependency Status

To use, list this package along with grunt-contrib-jshint and grunt-jscs in your package.json. Require the other packages from your Gruntfile.js normally (individually or via matchdep). Requiring this module returns a function with the following signature:

configurationHash = makeConfig(grunt, optionalArrayOfDirectoryNameStrings)

You can also get the .jscsrc and .jshintrc for your project by creating symbolic links in the root of your project to the copies of these files under node_modules/quick-grunt-config-coding-conventions/. (Obviously if you need customized versions of these files that differ from what this module provides, you should copy what you like and make an independent file in your project. If you edit these files via a symbolic link, your changes will be lost next time NPM updates the content of this package's directory.)

A Gruntfile.js that did nothing but install the configuration in this module could look like:

function configureGrunt(grunt) {
  require("matchdep").filterDev(["grunt-*", "!grunt-cli"]).forEach(grunt.loadNpmTasks);

  var configuration = {};
  _.merge(configuration, require("quick-grunt-config-coding-conventions")(grunt, ["build_components"]));

  grunt.initConfig(configuration);
}

module.exports = configureGrunt;

By default, the configurations created for the jshint and jscs tasks looks for '.js' in your projects root directory, and for all files matching `.js' in any directory under the directories 'app', 'lib', 'test', and 'spec'. You can include additional directory trees to scan for JavaScript files by including each tree's root directory name in the second optional array argument to the function returned from require.

Directories under any of the roots listed which match the patterns *node_modules* or *bower_components* are automatically excluded.

Contributions and suggestions are welcome, including a set of unit tests covering the existing behavior. Right now the "reference user" for this module is [https://github.com/ecdex/tsme.git(https://github.com/ecdex/tsme.git)]. Running 'grunt' in that repository after installing your modified version of this module should run clean, and should correctly find errors you introduce in JavaScript files in the 'app' and 'build_components' directories.

If you make/propose changes that are incompatible with the invokation in ecdex/tsme, please make a matching pull request against that repository.

If you want to introduce unit tests for this module, please introduce a set of development dependencies that are a subset of those in ecdex/tsme.

Wanted:

  • a patch that would remove non-existent and empty directories from the generated configuration.