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-shimney-sweeper

v1.2.5

Published

The sweeper housekeeps your shimney with grunt.

Downloads

11

Readme

shimney-sweeper Build Status

Housekeep your shimney with grunt.

install with npm

If you haven't used grunt before, be sure to check out the Getting Started guide.

From the same directory as your project's Gruntfile and package.json, install this plugin with the following command:

npm install grunt-shimney-sweeper --save-dev

Once that's done, add this line to your project's Gruntfile:

grunt.loadNpmTasks('grunt-shimney-sweeper');

If the plugin has been installed correctly, running grunt --help at the command line should list the newly-installed plugin's task or tasks. In addition, the plugin should be listed in package.json as a devDependency, which ensures that it will be installed whenever the npm install command is run.

usage

grunt sweepout

reads all your installed shimney packages exports them and writes a config for them.

grunt sweep-config

reads all your installed shimney packages from npm and writes your config to www/js/config.js.

grunt merge-configs

merges serval requirejs configuration together, into a new config file. The config file might be a module as a template and the merge of all configs can be adjusted

use

grunt.initConfig({
  "sweep-config": {
    www: {
      options: {
        configFile: "www/js/config.js",
        nodeModulesUrl: "../../" // with trailing slash, without node_modules/ appended
      }
    }
  },

  "sweepout": {
    test: {
      options: {
        //configFile: "build/js/config.js", // where to write the config to. Uses ${dir}/config.js as default
        // packageRoot: "tmp" // change this if your node_modules directory is not sibling to the gruntfile root
        //dir: "build/js" or specifiy the output-dir on commandline with --dir
      }
    }
  },

  "merge-configs": {
    rjsboot: {
      options: {
        targetFile: 'build/js/boot.js',

        configFiles: [
          'www/js/mylibrary/config.js',
          'www/js/config.js'
        ]

        modify: function(mergedConfig) { // can return or modify the mergedConfig that is written
          return { paths: {'user': 'overriden'} };
        }

        template: 'resources/config-template.js', // use this to inject the config in this file (will not be modified)
      }
    }
  }
});

in your Gruntfile.js to configure the sweeper.

your config-template.js used in merge-configs could be like this:

var require = {

}

if (typeof(requirejs) === "function") {
  requirejs.config(require);
}

This allows you to use the merged config before loading requirejs (recommended if you change the baseUrl) or as a data-main attribute in requirejs.

Migration

1.0.0 => 1.1.0

  • change config option into configFile

1.0.0 => 1.2.0

  • commands are now: sweepout, sweep-config, merge-configs
  • all commands are multi tasks