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

v0.3.0

Published

Plugin for generating $script manifest files which provides easier file management for bigger web apps

Downloads

15

Readme

grunt-smg

Plugin for generating $script manifests

Have you ever written script like this by hand?

$script([
    "/js/routes.js",
    "/bower_components/jquery/jquery.js",
    "/bower_components/angular-latest/lib/jquery/jquery.js"
], "1");
$script.ready("1", function () {
    $script([
        "/bower_components/bootstrap/js/transition.js",
        "/bower_components/bootstrap/js/tooltip.js",
        "/bower_components/bootstrap/js/tab.js",
        "/bower_components/bootstrap/js/scrollspy.js",
        "/bower_components/bootstrap/js/popover.js",
        "/bower_components/bootstrap/js/modal.js",
        "/bower_components/bootstrap/js/dropdown.js",
        "/bower_components/bootstrap/js/collapse.js",
        "/bower_components/bootstrap/js/carousel.js",
        "/bower_components/bootstrap/js/button.js",
        "/bower_components/bootstrap/js/alert.js",
        "/bower_components/bootstrap/js/affix.js",
        "/js/angular/angular.min.js"
    ], "2");
});
$script.ready("2", function () {
    $script(["/js/services/github.js",
        "/js/controllers/repos-ctrl.js",
        "/js/controllers/pulls-ctrl.js",
        "/js/controllers/main-ctrl.js",
        "/js/controllers/log-in-ctrl.js",
        "/js/controllers/issues-ctrl.js",
        "/js/angular/angular-route.min.js",
        "/js/main-dev.js",
        "/js/app.js"
    ], "scriptManifestReady");
});

Well this will generate it for you from much more concise notation using nice glob expressions:

 smg: {
    main:{
        steps: {
            1: [
                '**/jquery/jquery.js',
                '**/routes.js'
            ],
            2: ['public/js/**/angular.min.js', '**/bootstrap/js/*.js'],
            3: [
                'public/js/*.js',
                '**/angular-route.min.js',
                '**/js/controllers/*.js',
                '**/js/services/*.js'
            ]
        },
        relativeTo: 'public',
        dest: 'public/scriptLoader.js'
    }
 }

instead of providing an object, you can put your steps in a separate node module file and put relative path to the module file as a value for steps property. Like this:

 smg: {
    main:{
        steps: '/test/scriptManifest.js',
        relativeTo: 'public',
        dest: 'public/scriptLoader.js'
    }
 }

Getting Started

This plugin requires Grunt ~0.4

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

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

grunt.loadNpmTasks('grunt-smg');

The "smg" task

Overview

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

grunt.initConfig({
  smg: {
       steps: {     // each step will get transformed in it's own $script call
           1: ['public/**/*.js'],
           2: ['public/**/*.js'],
           3: ['public/**/*.js']
       },
       readyStr: 'scriptsReady',  // this string will be used as second param for $script call
       relativeTo: 'test/public',  // this path will be omitted from all url paths,
       dest: 'public/modules-definitions.js'
    },
})

Prefixed with @ all paths in the step will not be resolved via glob expressions, this can be used to specify remote URLs or paths which are not resolvable in build time.

'@1': ['...URL..'],