3 Commits

Author	SHA1	Message	Date
Greg Magolan	c5f2979a87	build(bazel): update to nodejs rules 0.31.1 & bazel 0.26.1 (#30965) ... * entry_point attribute of nodejs_binary & rollup_bundle is now a label * nodejs rules 0.30.1 has new feature to symlink node_modules with yarn_install and bazel 0.26.0 includes new managed_directories feature which enables this * Symlinking of node_modules for yarn_install temporarily disabled (except for integration/bazel) until the fix for https://github.com/bazelbuild/bazel/issues/8487 makes it into a future bazel release. This is needed to work-around issue: yarn_install & npm_install with managed directories can't handle deleted or manually regenerated node_modules folder [https://github.com/bazelbuild/rules_nodejs/issues/802]. Underlying issue has been fixed in Bazel https://github.com/bazelbuild/bazel/issues/8487 but hasn't landed in a release yet PR Close #30965	2019-06-11 10:54:28 -07:00
Greg Magolan	ea09430039	build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) ... PR Close #28871	2019-02-28 12:06:36 -08:00
Paul Gschwendtner	9de9c8ad03	fix(bazel): protractor utils cannot start server on windows (#27915) ... * Currently the protractor utils assume that the specified Bazel server runfile can be resolved by just using the real file system. This is not the case on Windows because the runfiles are not symlinked into the working directory and need to be resolved through the runfile manifest. PR Close #27915	2019-01-07 14:49:44 -08:00