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

v0.4.5

Published

A grunt wrapper for composer

Downloads

2,291

Readme

grunt-composer Build Status

A Grunt task wrapper for Composer, the PHP dependency manager.

Getting Started

Installing the plugin:

npm install grunt-composer --save-dev

Loading the plugin via JavaScript:

grunt.loadNpmTasks('grunt-composer');

grunt-composer is now ready to go!

Running Composer Commands

Simple task and multi task modes

grunt-composer supports both 'simple' and 'multi' task modes in Grunt. Multi task mode is activated whenever any configuration under the composer key is found in your Grunt configuration.

This is important, as the way you run the task changes depending on this mode.

Simple task mode

The first argument passed to the grunt-composer task becomes the command to run. Arguments are passed to tasks in Grunt by separating them via a colon, :.

grunt composer:update

is equivalent to:

composer update

Multi task mode

When in multi task mode, an additional target is required when running the task.

This example runs the composer update command, using configuration for the some_target target.

grunt composer:some_target:update

Command Options

You can provide arguments to the Composer executable by adding them to the task name you run. This pattern works for both simple and multi task modes.

grunt composer:install:no-dev

is equivalent to:

composer install --no-dev

Alternatively, you can provide these options through options in your Grunt configuration, explained below.

Options

Example configuration

grunt.initConfig({
    composer : {
        options : {
            usePhp: true,
            phpArgs: {
                someArg: 'custom'
            },
            flags: ['arg'],
            cwd: 'packages/build',
            composerLocation: '/usr/bin/composer'
        },
        some_target: {
            options : {
                flags: ['arg'],
                cwd: 'packages/build'
            }
        }
    }
})

options.usePhp

Type: Boolean Default value: false

This tells the plugin to execute php #{composerLocation}

options.flags

Type: Array Default value: []

This is an array of custom Composer CLI args, such as no-dev.
Note: This is bypassed if there are command options.

options.phpArgs

Type: Object Default value: {}

This is an object which you should use to send -D arguments to the php binary.

options.cwd

Type: String Default value: '.'

This is the working directory, normally where the composer.json is located.

options.composerLocation

Type: String Default value: 'composer'

The binary to use for Composer if not installed globally.

If options.cwd is present, relative paths for options.composerLocation are relative to that directory.