angular-cn/tools/gulp-tasks
Joey Perrott 200b770b85 build: revert back to downloading cldr-data directly rather than via npm (#39341)
Revert back to downloading cldr-data directly as the npm package seems
to no longer be maintained and additionally, it carries a ~350mb cost
in our node modules that is unnecessarily downloaded by most developers
and on CI.

PR Close #39341
2020-10-20 10:46:19 -07:00
..
cldr build: revert back to downloading cldr-data directly rather than via npm (#39341) 2020-10-20 10:46:19 -07:00
README.md build: migrate from gulp to ng-dev for running formatting (#36726) 2020-04-24 12:32:18 -07:00
changelog-zonejs.js build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
changelog.js build: filter out duplicate cherry-picked commits in changelog (#37956) 2020-07-08 12:04:46 -07:00
cldr.js build: revert back to downloading cldr-data directly rather than via npm (#39341) 2020-10-20 10:46:19 -07:00
platform-script-path.js build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
source-map-test.js build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00

README.md

Gulp Tasks folder

This folder contains one file for each task (or group of related tasks) for the project's gulpfile. The dependencies between the tasks is kept in the gulpfile.

Task File Structure

Each task is defined by a factory function that accepts gulp as a parameter. Each file exports either one factory or an object of factories.

E.g. The build.js file contains only one task:

module.exports = (gulp) => (done) => {
  ...
};

Loading Tasks

The tasks are loaded in the gulp file, by requiring them. There is a helper called loadTask(fileName, taskName) will do this for us, where the taskName is optional if the file only exports one task.

E.g. Loading the task that will run the build, from a task file that contains only one task.

gulp.task('build.sh', loadTask('build'));