Harp v0.14.0 – Implicit Autoprefixing
A new release of Harp is available today. Harp now takes care of vendor prefixing for you, via the fantastic Autoprefixer.
Create any .sass
, .scss
, .less
, or .styl
file…
// main.scss
h1 {
font-feature-settings: "liga";
transition: color 0.25s;
}
…and it will be preprocessed and prefixed automatically.
/* main.css */
h1 {
-webkit-font-feature-settings: "liga";
-moz-font-feature-settings: "liga";
font-feature-settings: "liga";
-webkit-transition: color 0.25s;
transition: color 0.25s
}
Get started
You shouldn’t have to think about vendor prefixing or configuring your preprossors while building static sites and apps. To get this taken care of for you, install the latest version of Harp:
npm install -g harp
Note you may need to preface this with sudo
depending on your setup. From there, make sure to take a look at Harp’s getting started guide.
Appropriate prefxing
To help keep unnecessary prefixes out, Harp and Autoprefixer only add the prefixes you actually need. For example, when you use the transition
property, the -moz-
prefix is actually no longer necessary. Therefore, it won’t be included:
h1 {
-webkit-transition: color 0.25s;
transition: color 0.25s
}
That’s one less thing you need to keep track of, and can even lighten your CSS over time as vendor prefixes are deprecated.
Preprocessor updates
We prefer to keep all of Harp’s preprocessors up-to-date. Since the last release, LESS and Stylus were updated with minor bug fixes.
- LESS is now at version 1.7.4, which includes various bug fixes.
- Stylus is now at version 0.47.3, which fixes support support for schema-less urls inside
url()
.
Going forward, we’ll apply this same approach to Autoprefixer, too.
Publish your project
Harp also helps power the Harp Platform, a front-end publishing integrated with Dropbox. It’s the fastest way to deploy your new project—you’ll never need to worry about manually compiling your files again.
Thanks
We love contributions to Harp and Terraform; Autoprefixer integration was suggested by @lunelson and kindly implemented by @geelen.
If you’re interested in contributing to Harp, just open an issue or comment on an existing one and let’s chat.
What’s next for Harp
We’re on track for more regular updates to Harp, and will be publishing a roadmap soon:
putting together Harp 1.0 Roadmap. BrowserSync and Browserify are coming. Going to be sweet.
— Brock Whitten (@sintaxi) September 10, 2014
Let us know if you’d like to be involved.