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

gruntfiles-mix

v0.0.8

Published

Combines tasks from multiple gruntfiles.

Downloads

5

Readme

Mix Gruntfiles!

Combines tasks from multiple Gruntfiles in sub folders.

Takes tasks Gruntfiles.js from (direct) child folders and combines them into single tasks list!

Installation

npm install gruntfiles-mix

After install if no Gruntfile.js in install directory the default one is created automatically:

/* Default gruntfile-mix Gruntfile.js */
module.exports = require('gruntfiles-mix')({
		addPrefix: true,
    	useNamePartAsPrefix: true,
    	prefixSeparator: '-'
});

You can use options to modify the behaviour

addPrefix

Type: Boolean Default value: false

Adds directory name as prefix to task name.

useNamePartAsPrefix

Type: Boolean Default value: true

Adds only first symbolic part for directory name as prefix (for directory "front-app" will take "front" as prefix).

prefixSeparator

Type: String Default value: -

Character(s) that separates prefix from task.

Gruntfiles with tasks

You typical grunt file in sub directories when used in Gruntfiles-mix scenario should modify supplied grunt config object and register needed tasks, but not initialize grunt configuration.

module.exports = function(grunt, config){

	// create your config if none is passed
	config = config || {}

	// define project/directory specific tasks
	grunt.loadNpmTasks('grunt-contrib-clean')

	// assume that clean tasks may already exist in config
	config.clean = config.clean || {}

    // to avoid problems with paths resolution prefer to use absolute paths in tasks (using ```__dirname```)
    // while execution of tasks CWD is Gruntfiles-mix dir, NOT __dirname of current Gruntfile.
	config.clean.dist = [__dirname + '/dist']

	// register custom task
	grunt.registerTask('clean-dist', ['clean:dist'])

	 // make possible to use this Gruntfile as usual (if only "grunt" argument is passed)
	 if (arguments.length == 1){
	    grunt.initConfig(config)
	 }
};

Caution!

Each time grunt.loadNmpTask in certain Gruntfile is executed it loads tasks (grunt module) from respective folder. If different Gruntfiles use the same modules with different versions tasks will be executed using last one loaded.

Tests

For test use command: node test