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

v1.0.0

Published

A Grunt plugin to simplify interoperation between Grunt and Make

Downloads

30

Readme

grunt-make Build Status via Travis CI NPM version

wat

Ease interoperability between Grunt and Make. Creates a "make" task that will automatically call the relevant target in your Makefile based on the arguments.

For more musings on why you would possibly want to do this, check out: http://aeflash.com/2014-10/make.html

Usage

grunt.loadNpmTasks("grunt-make");
//or
require("load-grunt-tasks")(grunt);

There is no configuration for the task itself. You would use the target in other compound tasks or as the target of a watcher.

For example, if you're building Sass with a grunt-contrib-watch, but you have you build configured with make, this is all you need to do in your Gruntfile:

//…
watch: {
  styles: {
    files: "styles/*.scss",
    task: "make:styles" // <--
  }
}
//…

...if your Makefile contains this:

styles: dist/css/main.css

dist/css/main.css: styles/*.scss
  node-sass styles/main.scss $@

You can also target files:

    //…
    task: "make:dist/css/main.css"
    //…

You can also specify many Make targets by separating them with colons:

gunt.registerTask("allthethings", ["make:styles:scripts:lint:doc:publish"]);

License

MIT