Keen Yee Liau 36902e2f0e fix(bazel): Bazel builder resolves with require.resolve() (#28478) ...

This commit fixes a bug in the Bazel builder in which the path to Bazel
executable is constructed using the project path. For non-default
project, the node_modules directory is actually one level above the
project path.

This PR fixes the bug by resolving node_modules with require.resolve().
It requires @bazel/bazel v0.22.1 because previous versions do not have
index.js or main field in package.json and would cause node module
resolution to fail.

This has been tested with both bazel and ibazel.

PR Close #28478

2019-02-01 13:56:53 -05:00

..

docs

docs(bazel): add skydoc generation (#23544)

2018-08-08 13:12:07 -07:00

src

fix(bazel): Bazel builder resolves with require.resolve() (#28478)

2019-02-01 13:56:53 -05:00

test

build: bump year (#27880)

2019-01-11 11:15:59 -08:00

BUILD.bazel

build: restrict visibility of npm_package targets (#27611)

2018-12-14 10:20:40 -08:00

check_version.js

fix(bazel): fix major/minor semver check between @angular/bazel npm packager version and angular bazel repo version (#27635)

2018-12-13 10:59:14 -08:00

index.bzl

build: use bazel version from node modules (#26691)

2018-10-30 16:19:13 -04:00

package.bzl

build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215)

2019-01-18 09:07:52 -08:00

package.json

fix(bazel): Bazel-workspace schematics should run in ScopedTree (#28349)

2019-01-28 12:00:16 -08:00

protractor-utils.js

build: idiomatic install of @angular/bazel npm package (#26258) (#26488)

2018-10-19 20:59:29 -07:00

yarn.lock

fix(bazel): Bazel-workspace schematics should run in ScopedTree (#28349)

2019-01-28 12:00:16 -08:00