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-ng-modules

v0.1.1

Published

An opinionated plugin for organizing Angular source code

Downloads

3

Readme

grunt-ng-modules

An opinionated plugin for organizing Angular source code

Allows devs to modularize their Angular code and separate it from distribution .js and .css files.

Module Structure

This plugin deals with Angular modules in a very strict way. Below is the recommended folder structure to be used in conjunction with the plugin

|-- /angular/modules (call this one whatever you want)
    |-- /module-one
    `-- /module-two
        |-- module.js
        |-- routes.js
        |-- /providers
        |-- /services
        |-- /controllers
        |-- /views
        `-- /directives
            |-- /directive-one
            `-- /directive-two
                |-- directive-two.js
                |-- directive-two.css
                `-- directive-two.html
                

In order to use this plugin you must have:

  • A folder for every module (the name of the folder is the name of the distribution files)
  • A module.js for every module (this must contain your module declaration, ie: angular.module('my-module', []) );

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-ng-modules --save-dev

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

grunt.loadNpmTasks('grunt-ng-modules');

The "ng_modules" task

Overview

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

grunt.initConfig({
  ng_modules: {
    options: {
      // Task-specific options go here.
    }
  },
});

Options

options.minify

Type: Boolean|String|Object Default value: false

Whether or not to create minified (.min.*) versions of the distribution files.

Can also be a string 'only'. If this is the value, only minified version of the files will be created.

Can also be an object, which allows you to specify .css and .js separately

minify: {
    css: 'only,
    js: true
}

options.jsDir

Type: String Default value: ''

The name of the directory where all .js files are copied to (appended to target.dest)

options.cssDir

Type: String Default value: ''

The name of the directory where all .css files are copied to (appended to target.dest)

options.viewDir

Type: String Default value: 'html'

The name of the directory where all view (.html) files are copied to.

options.cacheViews

Type: Boolean Default value: false

If true - the plugin will create an Angular module (named templates.{module-name}) and load all views for that module into the templateCache. This creates a new file, named {module-name}-templates.min.js

Targets

target.src

Type: String Default value: ''

The source directory where all modules are stored.

target.dest

Type: String Default value: ''

The destination directory where all distribution files should be created.

Usage Examples

grunt.initConfig({
  ng_modules: {
    options: {
      minify: true,
      viewDir: 'partials'
    },
    local: {
      src: 'angular/modules',
      dest: 'static/ng-modules'
    },
    production: {
      options: {
        cacheViews: true
      },
      src: 'angular/modules',
      dest: 'static/ng-modules'
    }
  },
});

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

(Nothing yet)