The Problem with gulp-util

Janiceilene
Dec 27, 2017 · 2 min read
Seeing this message?

A little postmortem

Last week we made gulp v4.0.0-alpha.3 available on GitHub and people are excited! We expected it to be breaking, but we didn’t realize the far reaching impact of the changes. This is due to 6,752 modules that depend on gulp-util; many of which utilize an extremely outdated version of Vinyl.

Why deprecation now?

We’ve been planning to deprecate gulp-util since 2014 because it’s just grab-bag of modules. Why would you want to download the beeper module if you’re only using gulp-util for logging? It drastically increases the download size of plugins and gulp itself. We had hoped people would transition to smaller modules, but it seems everyone continued with the status quo.

Help us fix the ecosystem

Using these steps, you can help plugin authors migrate away from gulp-util.

  1. For each dependent plugin, run npm issues {PLUGIN NAME} which will open their issue tracker.
  2. Open an issue or pull request to remove gulp-util using the following API replacements:

gulpjs

Curated gulp articles

gulpjs

Curated gulp articles

Janiceilene

Written by

Technical writer at GitHub. Content writer for gulp. Former Outreachy Intern for Systers. Mom to two tiny humans. (Views are my own)

gulpjs

Curated gulp articles