Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate away from gulp-util #284

Closed
mcman2017 opened this issue Mar 24, 2018 · 4 comments
Closed

Migrate away from gulp-util #284

mcman2017 opened this issue Mar 24, 2018 · 4 comments

Comments

@mcman2017
Copy link

Please use one/all of the following gulp replacements below:
using the following API replacements:
gutil.File => https://www.npmjs.com/package/vinyl
gutil.replaceExtension => The .extname property on Vinyl objects or https://www.npmjs.com/package/replace-ext
gutil.colors => https://www.npmjs.com/package/ansi-colors
gutil.date => https://www.npmjs.com/package/date-format
gutil.log => https://www.npmjs.com/package/fancy-log
gutil.template => https://www.npmjs.com/package/lodash.template
gutil.env => https://www.npmjs.com/package/minimist
gutil.beep => https://www.npmjs.com/package/beeper
gutil.noop => https://www.npmjs.com/package/through2
gutil.isStream => Use the .isStream() method on Vinyl objects
gutil.isBuffer => Use the .isBuffer() method on Vinyl objects
gutil.isNull => Use the .isNull() method on Vinyl objects
gutil.linefeed => Use the string '\n' in your code
gutil.combine => https://www.npmjs.com/package/multipipe
gutil.buffer => https://www.npmjs.com/package/list-stream
gutil.PluginError => https://www.npmjs.com/package/plugin-error

@zpao
Copy link
Member

zpao commented Mar 27, 2018

This was fixed in #279 (and just published)

@zpao zpao closed this as completed Mar 27, 2018
@demurgos
Copy link

demurgos commented Apr 8, 2018

@zpao
According to npm, gulp-util is still used. Could you check the published version? We're still getting issues on the Gulp side from users complaining about the deprecation warning caused by fbjs-scripts.

@zpao
Copy link
Member

zpao commented Apr 18, 2018

Thanks for catching that @demurgos! I was on a branch based on old master and totally messed that up. Luckily it was identical to v0.8.1 so no harm done. I just shipped v0.8.3 (double checking everything this time around).

@demurgos
Copy link

Looks good, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants