Naive regex matching breaks inlining with comments

Due to the way the inlining works with regex, when there is a comment that matches the pattern, the build fails. For example, this won’t build:

/**
@Component({
  selector: 'example',
  templateUrl: './example.component.html'
})
export class Example {
}
*/
@Component({
  selector: 'my-comp',
  template: '<div class="my-comp"></div>'
})
export class MyComponent {
}

It will fail with the following error:

Error: ENOENT: no such file or directory, open ‘/Users/user/Documents/project/src/app/comp/example.component.html’

Any chance of moving away from gulp-inline-ng2-template and into something like ts-simple-ast for inlining assets? Working with an AST would avoid this issue altogether.

Perhaps a workaround for now could be to remove comments before inlining.

[dherges]

Solved by #279

---

@elclanrs FYI

[elclanrs]

If it helps, this is how we inline assets currently, using the ts-simple-ast library: https://gist.github.com/elclanrs/c1944bf16cb8448b543872995db3ff82