What are the best workflow wrappers for front-end development?

Nowadays with the arrival of Node.js, front-end developers have more tools than ever at their disposal to help with their development process. One kind of these tools are workflow wrappers.

What workflow wrappers do is that they kickstart a project by installing the latest tools depending on the platform and project requirements and organizing the project’s folder using best practices. These tools are usually written in JavaScript and require Node to run.

Workflow wrappers have a scalable module architecture which means that they use third-party open source modules to scaffold projects and install dependencies. These modules are often called generators and usually can be built by anyone. Some workflow wrappers provide a special generator which is used to create a new generator depending on the project requirements.

Why do you recommend Yeoman?

Why do you not recommend Yeoman?

Active community

Yeoman has an active community with new generators being created at a rapid pace. Because of the momentum behind the community, you can expect good s...

Huge number of generators for scaffolding your project

Yeoman generators allow you to quickly set up a new project. Invoked with the scaffolding tool 'yo' they provide a boilerplate & tooling...

Combining Yeoman and backend frameworks can bring problems

Combining Yeoman and a backend framework such as Django, Rails or Laravel can create problem because the project structure of Yeoman may not be compa...

Why do you recommend CodeKit?

Why do you not recommend CodeKit?

Everything is set up for you

Everything you need to get a project started is included with CodeKit. Thanks to the professional support, different components of the workflow pipel...

Provides a clean and modern GUI

CodeKit has a clean and intuitive graphical user interface out of the box. Most other tools in this category run as command line utilities or require...

Mac only

This is a major problem for larger teams that have varied development environments.

Why do you recommend Slush?

Why do you not recommend Slush?

Built from the ground up to work with Gulp

Because Slush is built around streams and designed to work best with Gulp. It allows you to get the benefits of a streaming build system without havi...

Easier to maintain scaffolding through code

Because Slush is built on Gulp which puts code before configuration, scaffolding can be done in a simpler more straightforward way. Creating scaffold...

Still young with few generators available

Slush is still young compared to Yeoman. Although it has quite a few generators made by third parties and it's quite easy to make one yourself....

Why do you recommend Lineman?

Why do you not recommend Lineman?

Opinionated workflow

While Lineman is hands off when it comes to what you do on the client side, the workflow and tools used around it are opinionated, which means there&...

Comes with a full-featured test runner

Lineman integrates a powerful test runner - Test'em. By default it will test against PhantomJS and output in TAP13 format.

By trying it do everything by itself it has become a monolithic software

Lineman tries to minimize the work that the developer has to do but in doing so, it has become a complicated monolith of a software built on top of G...

Why do you recommend FireShell?

Why do you not recommend FireShell?

Provides a strong starting point built on best practices

FireShell is particularly opinionated, but it's a great way to get started with best practices if you're not sure where to start. It's a...

Small and has features that can be covered by Yeoman

FireShell is pretty small compared to Yeoman and it could have very well been a simple generator for Yeoman. This means that you can have the same fe...

Are we missing something?

Help make this question more complete.