0.33.2

0.33.2

0.33.1

• Fixes LINEMAN_ENV variable when used in conjunction with clean. Basically in any chained command, the presence of build will force the whole thing to "production". In the absence of "build", then "spec" or "spec-ci" will force the whole thing to "test". Otherwise the default ("development") or user set value will remain.

0.33.0

• Exposes process.env["LINEMAN_ENV"] to allow scripts & and config to branch based on whether run, spec, or build is running. This isn't really meant to be user-overridable, but will be set to "development" in all cases but spec, spec-ci (which are "test") and build (which is "production")
• Upgrades fetcher to support scripts that prepend and append content
• Adds a custom grunt task that emulates the lineman fetch CLI command.

When these powers, combine, lineman build scripts can now fetch (presumably volatile) third party dependencies as part of the build.

For example, if you configure your config/application.js to look like this:

  var prependCommonTasks = lineman.config.application.prependTasks.common;
  if(process.env["LINEMAN_ENV"] == "production") {
    prependCommonTasks = lineman.config.application.prependTasks.common.concat("fetch:facebook-connect-api-all:google-analytics:twitter-widgets-api");
  }

  return {
    prependTasks: {
      common: prependCommonTasks
    }
  };

Then facebook connect's API, twitter's widget API, and google analytics will all be fetched at build-time, which is desirable in the case of those dependencies, given their relative volatility and lack of application-facing APIs.

0.32.2

• Updates fetcher to 0.1.2, which fixes a glaring dependency error

0.32.1

• Updated fetcher dependency
• explicitly set the fetcher repo
• Improved archetype help message

This is a fun release b/c the new version of fetcher can install and prepare even multi-asset zip & tarball recipes. That means you can actually run:

$ lineman fetch bootstrap

And you'll have all of bootstrap's CSS, JS, and fonts placed where they need to be to just start working. (It'll print you a note about their JS lib relying on jQuery, which the user will have to deal with). Still, yay!

Here's how the vendor lib looks on a new project after running lineman fetch jquery bootstrap:

└── vendor
    ├── css
    │   ├── bootstrap-theme.css
    │   ├── bootstrap-theme.css.map
    │   ├── bootstrap.css
    │   └── bootstrap.css.map
    ├── img
    ├── js
    │   ├── bootstrap.js
    │   ├── jquery.js
    │   └── underscore.js
    └── static
        └── fonts
            ├── glyphicons-halflings-regular.eot
            ├── glyphicons-halflings-regular.svg
            ├── glyphicons-halflings-regular.ttf
            └── glyphicons-halflings-regular.woff

0.32.0

• lineman fetch can now fetch multiple recipes in a single command. For example lineman fetch ember backbone will fetch ember and backbone (and underscore, because backbone has a hard dependency on underscore)
• For quite a while app/static could be used to store arbitrary static assets that needed to be pathed relative to the site's / root, but now vendor/static will behave the same way (stuff in app will win in the event of a conflicting path). This will be used by future fetch recipes that need to ensure certain assets (like fonts and images) are available relative to JS or CSS at a certain path.

0.31.0

Adds a new lineman fetch <recipe> CLI command that simply fetches libraries to be added to your lineman project (saving you the step of browsing, downloading, and placing them yourself).

The library we're developing to enable this behavior is called "fetcher" and is available here: https://github.com/testdouble/fetcher

The list of available recipes is available here: https://github.com/linemanjs/fetcher-recipes/tree/master/recipes

Right now, only single-file recipes are supported. Soon, we'll add support for archive (zip/tar) recipes, git-based recipes, etc.

[It's worth noting that this is not meant to be a module replacement or an alternative to bower or browserify. This is simply a convenience for sucking down libraries with the intent of committing their assets into your project repo as vendored assets and concatenating them the old-fashioned way.]

0.30.0

• Add a --coffee flag when creating a new project. Switches example code to plain JS as a result. #263

0.29.3

• Upgrades testem #253 thanks @un33k!

0.29.2

• Upgrades grunt-watch-nospawn to address testdouble/grunt-watch-nospawn#2