# order-grunt-tasks

> ordering grunt 'task:target' strings via rules, applied in-order

Latest version **0.0.3** (published 2014-06-01) · BSD-2-Clause license · 0 weekly downloads

## Install

```sh
npm install order-grunt-tasks
pnpm add order-grunt-tasks
yarn add order-grunt-tasks
bun add order-grunt-tasks
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.0.3 |
| Published | 2014-06-01 |
| First published | 2014-06-01 |
| Weekly downloads | 0 |
| License | BSD-2-Clause |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 2 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Justin Searls |
| Maintainers | searls |

## Links

- npm: https://www.npmjs.com/package/order-grunt-tasks
- npm.io page: https://npm.io/package/order-grunt-tasks

## Dependencies (2)

- [underscore](https://npm.io/package/underscore.md) ^1.6.0
- [coffee-script](https://npm.io/package/coffee-script.md) ~1.7

## Recent versions

- 0.0.3 (latest) — 2014-06-01
- 0.0.2 — 2014-06-01
- 0.0.1 — 2014-06-01

## README

# order-grunt-tasks

**We're building this to provide a sane API for ordering build tasks
to [Lineman](https://github.com/linemanjs/lineman).**

## Background

Say you have a grunt config with some tasks and targets:

``` coffee
images: #<-- "images" task
  dev: {} #<-- "dev" target
  dist: {} #<-- "dist" target
```

In grunt, you could run "images" to run both tasks (in definition order),
or you could run "images:dev" to run just one target.

Let's suppose you have a build system that defines a default task-order:

```
tasks: ["coffee", "images:dev", "concat:dev"]
```

But suppose you discover that (for some reason), "images:dev" needs to
run after "concat:dev". You could, of course, just change the array.

But if you were somehow constrained to not modify the array directly,
but instead modify it dynamically, you'd be stuck reordering the array:

```
tasks: _(originalTasks).without("images:dev").concat("images:dev")
```

This gets hairy, though, if the difference between "images:dev" and "images"
is left to an only semi-meaningful string suffix. (Imagine dealing with
  multiple levels of task mutators)

What if, instead, it was initially assumed that all tasks were order-independent?
Then, rules could be added to an ordered list to describe ordering
requirements. So long as the task-mutator-manager (okay, conceit over: it's
Lineman) applies all the rules in order, then we're cool.

Some values:

taskTargets:
``` coffeescript
[
  { taskName: "coffee", targets: ["compile"] },
  { taskName: "images", targets: ["dev", "dist"] }
]
```

rules:
``` coffeescript
[
  {
    iWant: "images:dev"
    toBe: "after"
    these: "coffee"
  },
  {
    iWant: "coffee:compile"
    toBe: "before"
    these: ["images:dev","images:dist"]
  },
  {
    iWant: "coffee"
    toBe: "removed"
  }

]
```

---
_Source: https://npm.io/package/order-grunt-tasks · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._