gulp

I am using the gulp-notify plugin. This is an example of how I'm implementing it in a gulpfile.js ( You can see I'm using gutil and livereload as well. I don't know if they play any factors, but let me know if they do.) gulp.task('js', function() { return gulp.src('./dev/scripts/*.coffee') .pipe(coffee({bare: true}).on('error', gutil.log)) .pipe( gulp.dest('./build/js')) .pipe(notify('Coffeescript compile successful')) .pipe(livereload(server)); }); This plugin works on OS X and Linux. On Windows, which doesn't have a notification feature, it returns an error and breaks the gulp-watch plugin.

NPM philosophy, for better or worse, is to have all necessary dependencies for a project to be locally installed, in ./node_modules , and for package.json to reflect all necessary deps. I have a library, that would typically benefit from both global installation and local installation, similar to Gulp, Mocha, etc. One of the most insiduous problems with the above, is that the global and local versions might differ, causing compatibility issues for a given project. It occurred to me that we could avoid this problem, by creating an alias in .bash_profile , something like this: # bash psuedocode

I am trying to get gulp to compile my sass and use the susy grid/framework. I'm having troubles finding any information about this online. I have included: "gulp-ruby-sass": "^0.7.1", into my package.json and installed everything. My gulp sass gulp task likes like so: gulp.task('sass', ['images'], function () { return gulp.src('src/sass/*.{sass, scss}') .pipe(sass({ bundleExec: true, sourcemap: true, sourcemapPath: '../sass' })) .on('error', handleErrors) .pipe(gulp.dest('build')); }); So I can't for the life of me work out how to include susy so it complies using gulp , I haven't looked and

my package.json has scripts like this { "scripts": { "pretest": "npm run tsc", "test": "gulp e2e", } } we use typescript and webdriverIO for automation. I want to use gulp so that i can pass parameters to my test framework. Example: npm test --suite HomePageTests then the specs related to Home page must run. I have the gulp file like this // gulpfile.js const gulp = require('gulp'); const Launcher = require('webdriverio/build/lib/launcher'); const wdio = new Launcher(path.join(__dirname, 'src/config/conf.ts')); // fetch command line arguments const arg = (argList => { let arg = {}, a, opt,

I'm trying to use gulp-data with gulp-jade in my workflow but I'm getting an error related to the gulp-data plugin. Here is my gulpfile.js var gulp = require('gulp'), plumber = require('gulp-plumber'), browserSync = require('browser-sync'), jade = require('gulp-jade'), data = require('gulp-data'), path = require('path'), sass = require('gulp-ruby-sass'), prefix = require('gulp-autoprefixer'), concat = require('gulp-concat'), uglify = require('gulp-uglify'), process = require('child_process'); gulp.task('default', ['browser-sync', 'watch']); // Watch task gulp.task('watch', function() { gulp

At work we used to use Ruby to compile SCSS. I had the Ruby compiler set up as a file watcher in PhpStorm, and when I edited a partial imported by another file, the CSS file corresponding to the ancestor file was updated without any fuss. I want to get Gulp and Libsass to work the same way. Most solutions I've seen just compile all the SCSS files in a project when a single one changes, but our projects have way too much SCSS for that to be an acceptable solution. gulp-cached seemed like a great solution to this problem. But when I use gulp-cached the CSS output file doesn't change when I edit