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

v0.1.0

Published

grunt plugin for Appcelerator's Alloy framework for Titanium

Downloads

4

Readme

grunt-alloy

grunt plugin for Appcelerator's Alloy framework for Titanium

Getting Started

This plugin requires Grunt ~0.4.2

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

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

grunt.loadNpmTasks('grunt-alloy');

The "alloy" task

Overview

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

grunt.initConfig({
  alloy: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
});

Options

options.command

Type: String Default value: compile

The command to execute with alloy.

options.args

Type: Array, Default value: []

All the non-flag, non-option arguments to pass to alloy. For example, alloy new /path/to/project would be created as

grunt.initConfig({
  alloy: {
    all: {
      options: {
        command: 'new',
        args: ['/path/to/project']
      }
    }
  }
});

options...

The rest of the options and flags are the same as the those available to the Alloy CLI. You can see this list like this by typing alloy. The options should be named as camel case as opposed to the dashed format used by some of the CLI, making them easier to use as keys in your options. For example, --project-dir becomes projectDir. More details in the examples below.

flags

Flags like --no-colors should be given a boolean value.

grunt.initConfig({
  alloy: {
    all: {
      options: {
        command: 'compile',
        noColors: false
      }
    }
  }
});

Usage Examples

There's a few practical usage examples in this repo's Gruntfile.js. Aside from that, here's a few more examples.

Make a new Alloy project

Assuming the a traditional Titanium project already exists at /path/to/project, this would turn it into an Alloy project.

alloy: {
  all: {
    options: {
      command: 'new',
      args: ['/path/to/project']
    }
  }
}

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.