diff --git a/docs/CLI.md b/docs/CLI.md index daa3f5d09..685104125 100644 --- a/docs/CLI.md +++ b/docs/CLI.md @@ -1,10 +1,3 @@ - - ## gulp CLI docs ### Flags diff --git a/docs/FAQ.md b/docs/FAQ.md index 9c89c143a..f8a649ead 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -1,10 +1,3 @@ - - # FAQ ## Why gulp? Why not ____? diff --git a/docs/README.md b/docs/README.md index c783b710b..9b5955ac5 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,10 +1,3 @@ - - # gulp documentation * [Getting Started](getting-started/) - Get started with gulp diff --git a/docs/recipes/README.md b/docs/recipes/README.md index e1ec37211..3e822432a 100644 --- a/docs/recipes/README.md +++ b/docs/recipes/README.md @@ -1,10 +1,3 @@ - - # Recipes * [Automate release workflow](automate-release-workflow.md) diff --git a/docs/recipes/automate-release-workflow.md b/docs/recipes/automate-release-workflow.md index 3b929866a..0f18006a9 100644 --- a/docs/recipes/automate-release-workflow.md +++ b/docs/recipes/automate-release-workflow.md @@ -1,10 +1,3 @@ - - # Automate release workflow If your project follows a semantic versioning, it may be a good idea to automatize the steps needed to do a release. diff --git a/docs/recipes/browserify-multiple-destination.md b/docs/recipes/browserify-multiple-destination.md index fa1b65cec..474f58286 100644 --- a/docs/recipes/browserify-multiple-destination.md +++ b/docs/recipes/browserify-multiple-destination.md @@ -1,10 +1,3 @@ - - # Browserify + Globs (multiple destination) This example shows how to set up a task of bundling multiple entry points into multiple destinations using browserify. diff --git a/docs/recipes/browserify-transforms.md b/docs/recipes/browserify-transforms.md index 8659614ff..47a0d4d54 100644 --- a/docs/recipes/browserify-transforms.md +++ b/docs/recipes/browserify-transforms.md @@ -1,10 +1,3 @@ - - # Browserify + Transforms [Browserify](https://github.com/browserify/browserify) has become an important and indispensable diff --git a/docs/recipes/browserify-uglify-sourcemap.md b/docs/recipes/browserify-uglify-sourcemap.md index 99800ed53..58e622292 100644 --- a/docs/recipes/browserify-uglify-sourcemap.md +++ b/docs/recipes/browserify-uglify-sourcemap.md @@ -1,10 +1,3 @@ - - # Browserify + Uglify2 with sourcemaps [Browserify](https://github.com/browserify/browserify) has become an important and indispensable diff --git a/docs/recipes/browserify-with-globs.md b/docs/recipes/browserify-with-globs.md index d9396f1b6..72695fb6d 100644 --- a/docs/recipes/browserify-with-globs.md +++ b/docs/recipes/browserify-with-globs.md @@ -1,10 +1,3 @@ - - # Browserify + Globs [Browserify + Uglify2](https://github.com/gulpjs/gulp/blob/master/docs/recipes/browserify-uglify-sourcemap.md) shows how to setup a basic gulp task to bundle a JavaScript file with its dependencies, and minify the bundle with UglifyJS while preserving source maps. diff --git a/docs/recipes/combining-streams-to-handle-errors.md b/docs/recipes/combining-streams-to-handle-errors.md index 16b561669..7c38654af 100644 --- a/docs/recipes/combining-streams-to-handle-errors.md +++ b/docs/recipes/combining-streams-to-handle-errors.md @@ -1,10 +1,3 @@ - - # Combining streams to handle errors By default, emitting an error on a stream will cause it to be thrown unless it already has a listener attached to the `error` event. This gets a bit tricky when you're working with longer pipelines of streams. diff --git a/docs/recipes/cron-task.md b/docs/recipes/cron-task.md index ad90a6f01..316e0c9bc 100644 --- a/docs/recipes/cron-task.md +++ b/docs/recipes/cron-task.md @@ -1,10 +1,3 @@ - - # Run gulp task via cron job While logged in via a user that has privileges to run `gulp`, run the following: diff --git a/docs/recipes/delete-files-folder.md b/docs/recipes/delete-files-folder.md index 731ae4f91..59e9cc939 100644 --- a/docs/recipes/delete-files-folder.md +++ b/docs/recipes/delete-files-folder.md @@ -1,10 +1,3 @@ - - # Delete files and folders You might want to delete some files before running your build. Since deleting files doesn't work on the file contents, there's no reason to use a gulp plugin. An excellent opportunity to use a vanilla node module. diff --git a/docs/recipes/exports-as-tasks.md b/docs/recipes/exports-as-tasks.md index 892c6bbf5..2eaea4905 100644 --- a/docs/recipes/exports-as-tasks.md +++ b/docs/recipes/exports-as-tasks.md @@ -1,10 +1,3 @@ - - # Exports as Tasks Using the ES2015 module syntax you can use your exports as tasks. diff --git a/docs/recipes/fast-browserify-builds-with-watchify.md b/docs/recipes/fast-browserify-builds-with-watchify.md index aa07f1a93..5513068c2 100644 --- a/docs/recipes/fast-browserify-builds-with-watchify.md +++ b/docs/recipes/fast-browserify-builds-with-watchify.md @@ -1,10 +1,3 @@ - - # Fast browserify builds with watchify As a [browserify](https://github.com/browserify/browserify) project begins to expand, the time to bundle it slowly gets longer and longer. While it might start at 1 second, it's possible to be waiting 30 seconds for your project to build on particularly large projects. diff --git a/docs/recipes/handling-the-delete-event-on-watch.md b/docs/recipes/handling-the-delete-event-on-watch.md index ba7a77cd3..05bd683a1 100644 --- a/docs/recipes/handling-the-delete-event-on-watch.md +++ b/docs/recipes/handling-the-delete-event-on-watch.md @@ -1,10 +1,3 @@ - - # Handling the Delete Event on Watch You can listen for `'unlink'` events to fire on the watcher returned from `gulp.watch`. diff --git a/docs/recipes/incremental-builds-with-concatenate.md b/docs/recipes/incremental-builds-with-concatenate.md index 797bd0cab..c9fdaa0de 100644 --- a/docs/recipes/incremental-builds-with-concatenate.md +++ b/docs/recipes/incremental-builds-with-concatenate.md @@ -1,10 +1,3 @@ - - # Incremental rebuilding, including operating on full file sets The trouble with incremental rebuilds is you often want to operate on _all_ processed files, not just single files. For example, you may want to lint and module-wrap just the file(s) that have changed, then concatenate it with all other linted and module-wrapped files. This is difficult without the use of temp files. diff --git a/docs/recipes/maintain-directory-structure-while-globbing.md b/docs/recipes/maintain-directory-structure-while-globbing.md index 279eac11d..431d30b37 100644 --- a/docs/recipes/maintain-directory-structure-while-globbing.md +++ b/docs/recipes/maintain-directory-structure-while-globbing.md @@ -1,10 +1,3 @@ - - # Maintain Directory Structure while Globbing If you are planning to read a few files/folders from a directory and maintain their relative path, you need to pass `{base: '.'}` as the second argument to `gulp.src()`. diff --git a/docs/recipes/make-stream-from-buffer.md b/docs/recipes/make-stream-from-buffer.md index b376eafce..b7e44b955 100644 --- a/docs/recipes/make-stream-from-buffer.md +++ b/docs/recipes/make-stream-from-buffer.md @@ -1,10 +1,3 @@ - - # Make stream from buffer (memory contents) Sometimes you may need to start a stream with files that their contents are in a variable and not in a physical file. In other words, how to start a 'gulp' stream without using `gulp.src()`. diff --git a/docs/recipes/minified-and-non-minified.md b/docs/recipes/minified-and-non-minified.md index 3cc603a9e..e1a6a4296 100644 --- a/docs/recipes/minified-and-non-minified.md +++ b/docs/recipes/minified-and-non-minified.md @@ -1,10 +1,3 @@ - - # Output both a minified and non-minified version Outputting both a minified and non-minified version of your combined JavaScript files can be achieved by using `gulp-rename` and piping to `dest` twice (once before minifying and once after minifying): diff --git a/docs/recipes/minimal-browsersync-setup-with-gulp4.md b/docs/recipes/minimal-browsersync-setup-with-gulp4.md index 55a5ac38c..ec22c0717 100644 --- a/docs/recipes/minimal-browsersync-setup-with-gulp4.md +++ b/docs/recipes/minimal-browsersync-setup-with-gulp4.md @@ -1,10 +1,3 @@ - - # Minimal BrowserSync setup with Gulp 4 [BrowserSync](https://www.browsersync.io/) is a great tool to streamline diff --git a/docs/recipes/mocha-test-runner-with-gulp.md b/docs/recipes/mocha-test-runner-with-gulp.md index eab0725cd..c6ca3873f 100644 --- a/docs/recipes/mocha-test-runner-with-gulp.md +++ b/docs/recipes/mocha-test-runner-with-gulp.md @@ -1,10 +1,3 @@ - - # Mocha test-runner with gulp ### Passing shared module in all tests diff --git a/docs/recipes/only-pass-through-changed-files.md b/docs/recipes/only-pass-through-changed-files.md index 64d16dbe7..1b0a34496 100644 --- a/docs/recipes/only-pass-through-changed-files.md +++ b/docs/recipes/only-pass-through-changed-files.md @@ -1,10 +1,3 @@ - - # Only pass through changed files Files are passed through the whole pipe chain on every run by default. By using [gulp-changed](https://github.com/sindresorhus/gulp-changed) only changed files will be passed through. This can speed up consecutive runs considerably. diff --git a/docs/recipes/pass-arguments-from-cli.md b/docs/recipes/pass-arguments-from-cli.md index 40c44bc15..1f9c74b14 100644 --- a/docs/recipes/pass-arguments-from-cli.md +++ b/docs/recipes/pass-arguments-from-cli.md @@ -1,10 +1,3 @@ - - # Pass arguments from the command line ```js diff --git a/docs/recipes/rebuild-only-files-that-change.md b/docs/recipes/rebuild-only-files-that-change.md index d60a80257..245ddc4fb 100644 --- a/docs/recipes/rebuild-only-files-that-change.md +++ b/docs/recipes/rebuild-only-files-that-change.md @@ -1,10 +1,3 @@ - - # Rebuild only files that change With [`gulp-watch`](https://github.com/floatdrop/gulp-watch): diff --git a/docs/recipes/rollup-with-rollup-stream.md b/docs/recipes/rollup-with-rollup-stream.md index 4c77aacc1..24679d557 100644 --- a/docs/recipes/rollup-with-rollup-stream.md +++ b/docs/recipes/rollup-with-rollup-stream.md @@ -1,10 +1,3 @@ - - # Rollup with rollup-stream Like Browserify, [Rollup](https://rollupjs.org/) is a bundler and thus only fits naturally into gulp if it's at the start of the pipeline. Unlike Browserify, Rollup doesn't natively produce a stream as output and needs to be wrapped before it can take this position. [rollup-stream](https://github.com/Permutatrix/rollup-stream) does this for you, producing output just like that of Browserify's `bundle()` method—as a result, most of the Browserify recipes here will also work with rollup-stream. diff --git a/docs/recipes/run-grunt-tasks-from-gulp.md b/docs/recipes/run-grunt-tasks-from-gulp.md index ee633125f..51e95e5fb 100644 --- a/docs/recipes/run-grunt-tasks-from-gulp.md +++ b/docs/recipes/run-grunt-tasks-from-gulp.md @@ -1,10 +1,3 @@ - - # Run Grunt Tasks from Gulp It is possible to run Grunt tasks / Grunt plugins from within Gulp. This can be useful during a gradual migration from Grunt to Gulp or if there's a specific plugin that you need. With the described approach no Grunt CLI and no Gruntfile is required. diff --git a/docs/recipes/running-shell-commands.md b/docs/recipes/running-shell-commands.md index 7bc4eb1fe..5d3447476 100644 --- a/docs/recipes/running-shell-commands.md +++ b/docs/recipes/running-shell-commands.md @@ -1,10 +1,3 @@ - - # Running Shell Commands Sometimes it is helpful to be able to call existing command line tools from gulp. diff --git a/docs/recipes/running-task-steps-per-folder.md b/docs/recipes/running-task-steps-per-folder.md index 5ee3b6490..03ff5007b 100644 --- a/docs/recipes/running-task-steps-per-folder.md +++ b/docs/recipes/running-task-steps-per-folder.md @@ -1,10 +1,3 @@ - - # Generating a file per folder If you have a set of folders, and wish to perform a set of tasks on each, for instance... @@ -53,11 +46,11 @@ gulp.task('scripts', function(done) { // write to output .pipe(gulp.dest(scriptsPath)) // minify - .pipe(uglify()) + .pipe(uglify()) // rename to folder.min.js .pipe(rename(folder + '.min.js')) // write to output again - .pipe(gulp.dest(scriptsPath)); + .pipe(gulp.dest(scriptsPath)); }); // process all remaining files in scriptsPath root into main.js and main.min.js files diff --git a/docs/recipes/running-tasks-in-series.md b/docs/recipes/running-tasks-in-series.md index be60816fb..b28e692a3 100644 --- a/docs/recipes/running-tasks-in-series.md +++ b/docs/recipes/running-tasks-in-series.md @@ -1,10 +1,3 @@ - - # Running tasks in series By default, gulp CLI run tasks with maximum concurrency - e.g. it launches diff --git a/docs/recipes/server-with-livereload-and-css-injection.md b/docs/recipes/server-with-livereload-and-css-injection.md index 51b652268..a23cc239d 100644 --- a/docs/recipes/server-with-livereload-and-css-injection.md +++ b/docs/recipes/server-with-livereload-and-css-injection.md @@ -1,10 +1,3 @@ - - # Server with live-reloading and CSS injection With [BrowserSync](https://browsersync.io) and gulp, you can easily create a development server that is accessible to any device on the same WiFi network. BrowserSync also has live-reload built in, so there's nothing else to configure. diff --git a/docs/recipes/sharing-streams-with-stream-factories.md b/docs/recipes/sharing-streams-with-stream-factories.md index 932085235..16c110a06 100644 --- a/docs/recipes/sharing-streams-with-stream-factories.md +++ b/docs/recipes/sharing-streams-with-stream-factories.md @@ -1,10 +1,3 @@ - - # Sharing streams with stream factories If you use the same plugins in multiple tasks you might find yourself getting that itch to DRY things up. This method will allow you to create factories to split out your commonly used stream chains. diff --git a/docs/recipes/specifying-a-cwd.md b/docs/recipes/specifying-a-cwd.md index b6306d6a4..eba0ceca9 100644 --- a/docs/recipes/specifying-a-cwd.md +++ b/docs/recipes/specifying-a-cwd.md @@ -1,10 +1,3 @@ - - # Specifying a new cwd (current working directory) This is helpful for projects using a nested directory structure, such as: diff --git a/docs/recipes/split-tasks-across-multiple-files.md b/docs/recipes/split-tasks-across-multiple-files.md index efdd942fa..afee1be10 100644 --- a/docs/recipes/split-tasks-across-multiple-files.md +++ b/docs/recipes/split-tasks-across-multiple-files.md @@ -1,10 +1,3 @@ - - # Split tasks across multiple files If your `gulpfile.js` is starting to grow too large, you can split the tasks diff --git a/docs/recipes/templating-with-swig-and-yaml-front-matter.md b/docs/recipes/templating-with-swig-and-yaml-front-matter.md index dbda0ad14..50c98e5f7 100644 --- a/docs/recipes/templating-with-swig-and-yaml-front-matter.md +++ b/docs/recipes/templating-with-swig-and-yaml-front-matter.md @@ -1,10 +1,3 @@ - - # Templating with Swig and YAML front-matter Templating can be setup using `gulp-swig` and `gulp-front-matter`: diff --git a/docs/recipes/using-external-config-file.md b/docs/recipes/using-external-config-file.md index 4a2215d48..b073f1dfc 100644 --- a/docs/recipes/using-external-config-file.md +++ b/docs/recipes/using-external-config-file.md @@ -1,10 +1,3 @@ - - # Using external config file Beneficial because it's keeping tasks DRY and config.json can be used by another task runner, like `grunt`. diff --git a/docs/recipes/using-multiple-sources-in-one-task.md b/docs/recipes/using-multiple-sources-in-one-task.md index 6e5622ec4..39e3e3b23 100644 --- a/docs/recipes/using-multiple-sources-in-one-task.md +++ b/docs/recipes/using-multiple-sources-in-one-task.md @@ -1,10 +1,3 @@ - - # Using multiple sources in one task ```js diff --git a/docs/why-use-pump/README.md b/docs/why-use-pump/README.md index c4810725b..de6ebc85f 100644 --- a/docs/why-use-pump/README.md +++ b/docs/why-use-pump/README.md @@ -1,10 +1,3 @@ - - # Why Use Pump? When using `pipe` from the Node.js streams, errors are not propagated forward diff --git a/docs/writing-a-plugin/README.md b/docs/writing-a-plugin/README.md index d876250cd..bcd708356 100644 --- a/docs/writing-a-plugin/README.md +++ b/docs/writing-a-plugin/README.md @@ -1,10 +1,3 @@ - - # Writing a plugin If you plan to create your own Gulp plugin, you will save time by reading the full documentation. diff --git a/docs/writing-a-plugin/dealing-with-streams.md b/docs/writing-a-plugin/dealing-with-streams.md index d1ad36a87..777b11bff 100644 --- a/docs/writing-a-plugin/dealing-with-streams.md +++ b/docs/writing-a-plugin/dealing-with-streams.md @@ -1,10 +1,3 @@ - - # Dealing with streams > It is highly recommended to write plugins supporting streams. Here is some information on creating a gulp plugin that supports streams. diff --git a/docs/writing-a-plugin/guidelines.md b/docs/writing-a-plugin/guidelines.md index a1d626c93..b810ad8a1 100644 --- a/docs/writing-a-plugin/guidelines.md +++ b/docs/writing-a-plugin/guidelines.md @@ -1,10 +1,3 @@ - - # Guidelines > While these guidelines are totally optional, we **HIGHLY** recommend that everyone follows them. Nobody wants to use a bad plugin. These guidelines will actually help make your life easier by giving you assurance that your plugin fits well within gulp. diff --git a/docs/writing-a-plugin/recommended-modules.md b/docs/writing-a-plugin/recommended-modules.md index a2faa94ce..0b49b39d4 100644 --- a/docs/writing-a-plugin/recommended-modules.md +++ b/docs/writing-a-plugin/recommended-modules.md @@ -1,10 +1,3 @@ - - # Recommended Modules > Sticking to this curated list of recommended modules will make sure you don't violate the plugin guidelines and ensure consistency across plugins. diff --git a/docs/writing-a-plugin/testing.md b/docs/writing-a-plugin/testing.md index cc9f98469..487a87f95 100644 --- a/docs/writing-a-plugin/testing.md +++ b/docs/writing-a-plugin/testing.md @@ -1,10 +1,3 @@ - - # Testing > Testing your plugin is the only way to ensure quality. It brings confidence to your users and makes your life easier. diff --git a/docs/writing-a-plugin/using-buffers.md b/docs/writing-a-plugin/using-buffers.md index b7ea05548..e35e41b59 100644 --- a/docs/writing-a-plugin/using-buffers.md +++ b/docs/writing-a-plugin/using-buffers.md @@ -1,10 +1,3 @@ - - # Using buffers > Here is some information on creating gulp plugin that manipulates buffers.