Browserify relative template paths

[michaelknoch]

Implement relative url to inline html transformation in browserify gulp task.
This adds the possibility to use relative template urls.

[Yimiprod]

Maybe you can inherit options? That way ng2TemplateParser can use target or we can change base options

[Yimiprod]

After having tested it there's one problem, watching the html to run the build doesn't work correctly, the build is done but the transform isn't applied, so we don't see any changes, the only thing that work is to reload the build.

[michaelknoch]

yes, you are right @Yimiprod.
It would be possible to trigger browserify build with ng2TemplateParser transformation again when html has changed, but i'm not sure if this will feel comfortable, because the process takes some seconds for me.

[Yimiprod]

Tried something that "almost" work:

  var b = browserify(options.src, options.browserifyOptions)
    .plugin(tsify, options.tsifyOptions);

  if (options.watch) {
    watchify(b, options.watchifyOptions);
    b.on('update', bundle);
    b.on('log', options.onLog);
  }

  b.transform(function(file) {
      return through(function (buf, enc, next) {
        ng2TemplateParser({contents: buf, path: file}, options.browserifyOptions)((err, result) => {
          this.push(result);
          process.nextTick(next);
        });
      });
    });

That way, if we change the template, it not trigger rebuild BUT if we change the controller who call that template, the build is correctly done.