iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(bazel): incorrectly always uses ngc-wrapped from "npm" workspace (#28137)

Browse Source 
* This is a follow-up to cd0451305a which fixes that "ngc-wrapped" from the "npm" workspace is always used if "angular" is fetched as an external dependency.

PR Close #28137
This commit is contained in:
Paul Gschwendtner 2019-01-14 22:15:18 +01:00 committed by Andrew Kushnir
parent 68bdbf0520
commit d12db4e114
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
packages/bazel/src/esm5.bzl
View File

@ -96,10 +96,10 @@ def _esm5_outputs_aspect(target, ctx):
compiler = ctx.executable._ngc_wrapped compiler = ctx.executable._ngc_wrapped
# BEGIN-INTERNAL # BEGIN-INTERNAL
# If the "replay_compiler" path refers to "ngc_wrapped" from within the Angular workspace, # If the "replay_compiler" path does not refer to "ngc_wrapped" from the "@npm" workspace,
# we need to use "ngc_wrapped" from source. This is necessary because we don't have # we use "ngc_wrapped" from within the Angular workspace. This is necessary because we
# a "npm" workspace with the "@angular/bazel" NPM package installed. # don't have a "npm" workspace with the "@angular/bazel" NPM package installed.
if not replay_compiler_path.startswith("../"): if replay_compiler_path != ctx.executable._ngc_wrapped.short_path:
compiler = ctx.executable._internal_ngc_wrapped compiler = ctx.executable._internal_ngc_wrapped
# END-INTERNAL # END-INTERNAL