angular-docs-cn/tools/gulp-tasks
Chuck Jazdzewski f96142cd7c build: remove references to `tsc-wrapped` (#19298)
With this commit `ngc` is used instead of `tsc-wrapped` for
collecting metadata and tsickle rewriting and `tsc-wrapped`
is removed from the repository.

`@angular/tsc-wrapped@5` is now deprecated and is no longer
used, updated, or maintained as part as of Angular 5.x.x.

`@angular/tsc-wrapped@4` is still maintained and required by
Angular 4.x.x and will be maintained as long as 4.x.x is in
LTS.

PR Close #19298
2017-09-21 13:55:52 -07:00
..
cldr refactor(common): export locale data from closure-locale (#18973) 2017-08-31 11:23:12 -07:00
README.md build: add the `tslint` gulp task (#14481) 2017-02-14 14:16:50 -08:00
build.js build: do not create the bundles when updating the public API 2017-05-17 08:34:50 -07:00
changelog.js build: modularize the gulp file to be easier to maintain (#14259) 2017-02-03 00:10:41 -08:00
check-cycle.js build: modularize the gulp file to be easier to maintain (#14259) 2017-02-03 00:10:41 -08:00
cldr.js feat(common): generate `closure-locale.ts` to tree shake locale data (#18907) 2017-08-29 11:26:10 -05:00
format.js build: publish tree of files rather than FESMs (#18541) 2017-08-31 15:34:50 -07:00
lint.js build: remove references to `tsc-wrapped` (#19298) 2017-09-21 13:55:52 -07:00
platform-script-path.js build: modularize the gulp file to be easier to maintain (#14259) 2017-02-03 00:10:41 -08:00
public-api.js build: update public api file names (#19190) 2017-09-19 16:59:18 -07:00
serve.js build: modularize the gulp file to be easier to maintain (#14259) 2017-02-03 00:10:41 -08:00
source-map-test.js build: remove references to `tsc-wrapped` (#19298) 2017-09-21 13:55:52 -07:00
tools-build.js build: modularize the gulp file to be easier to maintain (#14259) 2017-02-03 00:10:41 -08:00
validate-commit-message.js ci: simplify validate-commit-message empty line logic 2017-02-16 14:57:23 -08: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) => {
  ...
};

E.g. The format.js file contains two tasks:

module.exports = {
  // Check source code for formatting errors (clang-format)
  enforce: (gulp) => () => {
    ...
  },

  // Format the source code with clang-format (see .clang-format)
  format: (gulp) => () => {
    ...
  }
};

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'));

E.g. Loading the task that will enforce formatting, from a task file that contains more than one task:

gulp.task('format:enforce', loadTask('format', 'enforce'));

E.g. Loading a task that has dependencies:

gulp.task('lint', ['format:enforce', 'tools:build'], loadTask('lint'));