Add an option to use a fork of ng-annotate #40
Conversation
ng-annotate is no longer maintained[1], and hence fails when applied to source code containing modern JavaScript constructs, like import and export. In particular, this prevents usage with Webpack's ES6 modules support (issue andrey-skl#17). [1] olov/ng-annotate#245 To work around it, allow the user to specify a fork of ng-annotate, which adds support for new JS syntax.
|
I created such a fork here: https://github.com/bluetech/ng-annotate-patched and published it to npm under the name |
|
Regarding the unrelated travis failure, I think the problem is caused by typescript, which for some reason emits its code with |
|
@bluetech Yeah I have researched it recently and it uses different new line symbols on Mac and Linux, so it is known issue and build doesn't pass at the moment. |
|
Thank you! Would you mind publishing a release with this commit? I know you had already made one just the other day - sorry about that. Then I would post instructions in the issue on how to use my fork, if people want to do so; it works fairly well on my codebase with Webpack2 and ES6 modules. |
|
@bluetech published as 0.6.0 – you're welcome. |
ng-annotate is no longer maintained[1], and hence fails when applied to
source code containing modern JavaScript constructs, like import and
export. In particular, this prevents usage with Webpack's ES6 modules
support (issue #17).
[1] olov/ng-annotate#245
To work around it, allow the user to specify a fork of ng-annotate,
which adds support for new JS syntax.