I took this from the Gulp documentation:
const { series, parallel } = require('gulp');
function clean(cb) {
console.log("clean");
cb();
}
function css(cb) {
console.log("css");
cb();
}
function javascript(cb) {
console.log("javascript");
cb();
}
exports.build = series(clean, parallel(css, javascript));
When I run this with gulp build, I get:
Task never defined: build
If I run ./node_modules/.bin/gulp build, it works.
And if I change the exports to:
exports.build = css
and run with gulp build, then it works too.
What am I doing wrong?
I've tried this on the WSL (Linux, my default env), but also on Windows directly. Another developer on my team doesn't have this issue, although he is running on a Mac. I've also tried different versions of Node.
Updating from gulp v4.0.0 to v4.0.1 fixes this issue.
Issue is with local vs global version of gulp.
use 'node gulp build' or 'yarn gulp build' (if you are using yarn)
This will solve your issue.
Related
I'm trying to set up gulp in an MVC Core project within VS 2017. I have what I believe to be a valid gulpfile.js:
var gulp = require('gulp');
var rimraf = require('rimraf');
var concat = require('gulp-concat');
var cssmin = require('gulp-cssmin');
var uglify = require( 'gulp-uglify' );
var paths = {
webroot: './wwwroot/',
};
paths.js = paths.webroot + 'js/**/*.js';
paths.minJs = paths.webroot + 'js/**/*.min.js';
paths.css = paths.webroot + 'css/**/*.css';
paths.minCss = paths.webroot + 'css/**/*.min.css';
paths.concatJsDest = paths.webroot + "js/site.min.js";
paths.concatCssDest = paths.webroot + "css/site.min.css";
gulp.task("clean:js", function (cb) {
rimraf(paths.concatJsDest, cb);
});
gulp.task("clean:css", function (cb) {
rimraf(paths.concatCssDest, cb);
});
gulp.task( "clean", ["clean:js", "clean:css"] );
But when I open Task Runner Explorer I get the message "(no tasks found)".
I've checked to ensure all the gulp packages were installed via npm. I also added a package.json file. But the tasks are still not being found.
What am I doing wrong?
Apparently you have to install gulp locally within your project for it to work properly with Visual Studio. Global install won't work. Deleting the global copy and installing it locally solved the problem.
I was faced the same issue, and fix this after running two commands. Please refer below the process:
1) Right click on your gulp file in visual-studio, and choose "Open Command Line > PowerShell"
2) Run the command npm install gulp for install gulp. (You have to install gulp in your project, no matter if you have already installed gulp globally, but in this case you have to install the gulp in your project)
and press enter.
3) After execution of command go to task runner explorer in Visual-Studio and press the refresh button.
After pressing the refresh button you will see all your task list under task runner.
If you found any error related to "missing module" in output window like below:
Then you have to install missing npm plugins, for this just run the below command (into powershell):
npm install and press enter.
This command will install all the missing plugin, refer below image:
And then press again the refresh button in task runner explorer and you will see all your gulp task list under task runner window.
Hope this solution will help.
You need to have all the dependencies installed too - my VS Task Runner was failing without any error messages on a new install - I had already installed gulp locally, but my gulpfile.js showed the following required modules:
var util = require('gulp-util'),
gulp = require("gulp"),
concat = require("gulp-concat"),
cssmin = require("gulp-cssmin"),
rename = require('gulp-rename'),
babel = require('gulp-babel'),
terser = require("gulp-terser")
//del = require("del");
;
One of them was missing, so I ran
npm install gulp-util
npm install gulp-concat
npm install gulp-cssmin
npm install gulp-rename
npm install gulp-babel
npm install gulp-terser
And the task runner displayed my tasks - one of the modules weren't loading properly. Odd behaviour because the gulpfile.js and task runner were working correctly last week and the only changes made have been to install a few unrelated node modules locally.
In my case, I'd already installed gulp (prior to this, Task Runner Explorer was saying "Failed to load" under Gulpfile.js like this)
But I still had "No tasks found" like this
Additionally, Visual Studio had already told me that it had installed all the required node packages when I asked it to convert my bundleconfig.json to gulp. But despite all of this, gulp still wasn't happy (and the node_modules directory under my web app root was pretty empty).
Running "npm install gulp" again I noticed this in the commandline
and thought this might be a write permission problem because package.json is under source control in my project. I checked that out and re-ran "npm install gulp" and similar for the associated packages like gulp-concat and now I have a very full node_modules directory and... does gulpfile.js work? Well no but I've got a different error now so I'm pretty sure that I'm on to a different problem now :-/
TL;DR; make sure your package.json is checked out before you start installing node packages if you're using source control.
In my case, I had the same. I installed all requirements but still, gulp did not work on task runner explorer, threw no tasks found. I solved it by unchecking the $(VSInstalledExternalTools).
Tools > Options > Projects and Solutions > Web Package Management > External Web Tools
I can run a task with a flag via:
gulp build --production
Is there anyway to have a task set up like this:
gulp.task('deploy',
gulp.series('build'));
And also include the flag:
gulp.task('deploy',
gulp.series('build --production'));
So I could just call gulp deploy to run a production build?
Since this is not really possible using the built-in gulp functionality, I wrote a package that makes this as easy and convenient as possible: gulp-parameterized.
(Note: this is still a work in progress. For one thing it needs a comprehensive test suite. It's also severely lacking in documentation. However the core functionality has been tested and should work.)
Here's your example using gulp-parameterized:
var gulp = require('gulp');
var parameterized = require('gulp-parameterized');
gulp.task('build', parameterized(function(_) {
if (_.params.production) {
/* production build */
} else {
/* development build */
}
}));
gulp.task('deploy', parameterized.series('build --production'));
This also automatically parses command line flags, so you don't need to parse those yourself with yargs anymore.
The following commands create production builds:
$ gulp build --production
$ gulp deploy
While the following commands create development builds:
$ gulp build
$ gulp build --no-production
I am trying to run the Aurelia skeleton-es2016-asp.net5 demo.
I am following the steps in read me.
I opened a command box and ran
npm install gulp
which seemed to work
however ehrn I now run
gulp watch
I get an error
No gulpfile found
Have you created gulpfile.js containing the gulp tasks ?
If No, you need to add gulpfile.js to your directory root and may write some default task in it for testing,
var gulp = require('gulp');
gulp.task('default', function () { console.log('Hello Gulp!') });
If yes, Try Installing gulp globally npm install -g gulp
I've been toiling with this for a number of hours now and figured I best get some help as I'm going in circles.
I'm relatively new to using Gulp but quite excited to be doing so. I have a very simple gulpfile.js setup as below:
var gulp = require('gulp');
var sass = require('gulp-sass');
gulp.task('sass', function () {
gulp.src('./sass/**/*.scss')
.pipe(sass())
.pipe(gulp.dest('./css'));
console.log("ran something");
});
gulp.task('watch', function () {
gulp.watch('./sass/**/*.scss', ['sass']);
});
This all executes just fine. However, my scss files only get compliled when I first execute gulp. The watch recognises all changes when I make them but no further compiles are made. It's almost like the file gets locked or cached or something strange after it is first initiated.
Here is cli output:
[15:04:04] Starting 'watch'...
[15:04:04] Finished 'watch' after 11 ms
[15:04:12] Starting 'sass'...
ran something
[15:04:12] Finished 'sass' after 8.17 ms
I'm running Windows 10 64bit and fresh install of gulp and dependencies as of today.
My primary editor is PhpStorm in which I've setup a configuration to run the gulp file. However, I've also tried in a basic text editor as well as running gulp directly from the node command prompt.
Any ideas?
Appears as though the issue wasn't an issue with gulp or any of the setup above. I noticed if I watched the files outside of all my editors that they were indeed being updated via gulp and it was just my editors that weren't responding until I stopped the gulp watch.
I trialled the latest version of PhpStorm 10 and it worked perfectly first time even though nothing else has changed. Must simply be a bug in version 8 seeming Gulp didn't exist back then.
When I run the gulp task (default) for the first time, the sass task gives an error on a Bower package. More specifically on Susy.
The error:
Plumber found unhandled error:
Error in plugin 'gulp-sass'
Message:
file to import not found or unreadable: su/utilities
Current dir: /Users/Jeroen/sites/gulp/bower_components/susy/sass/susy/
The Susy bower package is being installed successfully with gulp-bower, taking its information from my bower.json file. However, when the default task gets to the sass task, it can't find Susy.
style.scss
#import "../bower_components/susy/sass/susy";
This only occurs when I run gulp for the first time. The watch task doesn't stop/breaks after this error, and keeps working after. (I can compile sass without a problem).
But it looks abit messy, any ideas on how I can prevent this?
You can see my entire gulpfile.js here:
https://gist.github.com/JeroenDelbrk/798d646af5cc2ad78da0
Tips on how I can improve my gulpfile, unrelated to this question, are also welcome.
In this line
gulp.task('default', ['bower', 'sass', 'scripts', 'imagemin', 'iconfont', 'watch']);
All of the tasks are getting executed in parallel. Which is fine if you don't have any dependencies. However, judging from your explanations, a successful run of sass is strongly dependent on a successful execution of bower. At the time you run sass, bower might not be finished, thus not providing the files you need.
To solve that in Gulp 3.*, you need to wire your dependencies right. I'd suggest the following:
// Define plugins
var gulp = require('gulp'),
gulpLoadPlugins = require('gulp-load-plugins');
$ = gulpLoadPlugins();
gulp.task('bower', function() {
return $.bower()
.pipe(gulp.dest('./bower_components'))
});
// Sass compile + prefix task
gulp.task('sass', ['bower'], function(){
...
});
// Default Task
gulp.task('default', ['sass', 'scripts', 'imagemin', 'iconfont']);
// Watch Task
gulp.task('watch', ['default'], function(){
gulp.watch('sass/**/*.scss', ['sass']);
gulp.watch('js/*.js', ['scripts']);
gulp.watch('originals/*', ['imagemin']);
gulp.watch('icons/*.svg', ['iconfont']);
});
And ruf gulp watch. This will execute all tasks which can be run in parallel at the same time, but bower will be executed before sass. One problem you might face: Running bower everytime you'll execute sass. That's why we will use gulp-changed to prevent reruns.
gulp.task('bower', function() {
return $.bower()
.pipe(changed('./bower_components'))
.pipe(gulp.dest('./bower_components'))
});
Hope this helps