Question 1

How do I set up Wellington with Gulp?

Accepted Answer

Install the Gulp plugin and configure it in your gulpfile.js; the project provides a working example in the examples/gulp directory that demonstrates watch and compile tasks for easy integration.

Question 2

Is Wellington faster than Compass for spriting?

Accepted Answer

Yes, benchmarks in the README show Wellington can be up to 20x faster on large projects with many images, thanks to its use of libsass and Go, making it a practical alternative for performance-critical workflows.

Question 3

Can Wellington handle retina or high-DPI sprites?

Accepted Answer

The documentation doesn't explicitly cover retina support; it focuses on basic spriting functions, so developers may need to implement custom Sass mixins or external tools for multi-resolution image handling.

Question 4

What's the easiest way to migrate from Compass to Wellington?

Accepted Answer

Replace Compass with Wellington in your build process and verify your Sass uses only supported spriting functions; the drop-in compatibility makes migration straightforward, but unsupported flags may require adjustments.

Question 5

Does Wellington work without using spriting features?

Accepted Answer

Yes, it can compile standard Sass via libsass, but its main value is in spriting and image operations; for plain Sass compilation, other libsass tools like node-sass might be simpler and more widely supported.

Question 6

Is Wellington still actively maintained?

Accepted Answer

The README shows CI and coverage badges, but benchmarks date from 2015, indicating it may be stable but not rapidly evolving; check the GitHub repository for recent commits or issues to gauge current activity.

wellington

What is wellington?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions