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

v0.0.1

Published

Conventionally init your configurations

Downloads

1

Readme

grunt-initconfig

Seperate your long configuration. It conventionally init your configurations.

Getting Started

Install the module with: npm install grunt-initconfig --save-dev

Then add this line to your project's Gruntfile.js gruntfile:

grunt.loadNpmTasks('grunt-initconfig');

You can run initconfig task:

grunt.task.run('initconfig');

grunt.registerTask('dev', 'lint server watch');
grunt.registerTask('prod', 'lint test');

Otherwise:

grunt.registerTask('dev', 'initconfig lint server watch');
grunt.registerTask('prod', 'initconfig lint test');

Documentation

grunt-initconfig support a lot of formats. Choose your favorate:

  • .yaml: yaml
  • .json: json
  • .js: JavaScript
  • .cson: cson
  • .coffee: CoffeeScript
  • .md: mdconf

Put your configuration files in .initconfig. grunt-initconfig automatically load and initialize configurations in .initconfig directory. Let's see examples:

$ tree -a
.
└── .initconfig
    ├── clean.json
    ├── coffee
    │   ├── tasks.coffee
    │   └── test.coffee
    ├── coffeelint.coffee
    ├── copy.yaml
    ├── jshint.js
    ├── simplemocha.md
    └── watch.cson

All of configuration will be injected into 'grunt config'.

In .initconfig, directory is a namespace. Next two examples is the same.

.initconfig/coffee-tasks.coffee:

module.exports = (grunt)->
  coffee:
    tasks:
      expand: true
      cwd: 'src/tasks/'
      src: ['**/*.coffee']
      dest: 'tasks/'
      ext: '.js'

.initconfig/coffee/tasks.coffee:

module.exports = (grunt)->
  tasks:
    expand: true
    cwd: 'src/tasks/'
    src: ['**/*.coffee']
    dest: 'tasks/'
    ext: '.js'

Examples

.yaml:

copy:
  tasks:
    files:
      - expand: true
        cwd: src/tasks
        src:
          - '**/*.js'
        dest: tasks/
  test:
    files:
      - expand: true
        cwd: src/test
        src:
          - '**/*.js'
        dest: out/test

.json:

{
  "clean": [
    "out/",
    "tasks/",
    "*.js",
    "*.js.map",
    "src/**/*.js",
    "src/**/*.js.map"
  ]
}

.js:

module.exports = function(grunt) {
  return {
    jshint: {
      options: {
        jshintrc: '.jshintrc'
      },
      tasks: {
        src: ['src/tasks/**/*.js']
      },
      test: {
        src: ['src/test/**/*.js']
      }
    }
  };
};

.cson:

{
  watch:
    gruntfile:
      files: '<%= coffeelint.gruntfile.src %>'
      tasks: [
        'coffeelint:gruntfile'
      ]
    jsTasks:
      files: '<%= jshint.tasks.src %>'
      tasks: [
        'jshint:tasks'
        'test'
      ]
    jsTest:
      files: '<%= jshint.test.src %>'
      tasks: [
        'jshint:test'
        'test'
      ]
    coffeeTasks:
      files: '<%= coffeelint.tasks.src %>'
      tasks: [
        'coffeelint:tasks'
        'coffee:tasks'
        'test'
      ]
    coffeeTest:
      files: '<%= coffeelint.test.src %>'
      tasks: [
        'coffeelint:test'
        'coffee:test'
        'test'
      ]
}

.coffee:

module.exports = (grunt)->
  coffeelint:
    gruntfile:
      src: 'Gruntfile.coffee'
    tasks:
      src: ['src/tasks/*.coffee']
    test:
      src: ['src/test/*.coffee']
    options:
      no_trailing_whitespace:
        level: 'error'
      max_line_length:
        level: 'warn'

.md:

# simplemocha

## options

Blur Blur Blur

- timeout: 3000
- ignoreLeaks: false
- ui: bdd
- reporter: spec

### globals
  - should

## test

`test` is target

### src

[mocha]() requires these files like `--require` options

- node_modules/should/lib/should.js
- out/test/**/*.js

Contributing

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

  • 2013-08-25 v0.0.1 Release grunt-initconfig

License

Copyright (c) 2013 Changwoo Park Licensed under the MIT license.