angular-docs-cn

Commit Graph

Author	SHA1	Message	Date
Joey Perrott	c043ecf317	fix(dev-infra): allow build-worker to be used in forked process (#40012 ) Generates a local copy of the build-worker file to allow it to be loaded at runtime in a forked process. PR Close #40012	2020-12-08 12:06:51 -08:00
Paul Gschwendtner	69472a1ed0	refactor(dev-infra): allow for consumption with rules_nodejs v2.0.0 (#37968 ) With `rules_nodejs` v2.0.0 being in RC phase currently, we should make sure that the package is compatible so that we can use it in the components repo in combination with rules_nodejs v2.0.0. In v2.0.0 of the NodeJS rules, Bazel workspaces are recommended to no longer be symlinked under a separate repository. Instead, bazel rules and targets should be accessed directly from the user-selected NPM repository. Usually `@npm`, so that the import changes to `@npm//@angular/dev-infra-private/<..>`. PR Close #37968	2020-07-13 14:18:22 -07:00

Author

SHA1

Message

Date

Joey Perrott

c043ecf317

fix(dev-infra): allow build-worker to be used in forked process (#40012 )

Generates a local copy of the build-worker file to allow it to be loaded
at runtime in a forked process.

PR Close #40012

2020-12-08 12:06:51 -08:00

Paul Gschwendtner

69472a1ed0

refactor(dev-infra): allow for consumption with rules_nodejs v2.0.0 (#37968 )

With `rules_nodejs` v2.0.0 being in RC phase currently, we should
make sure that the package is compatible so that we can use it
in the components repo in combination with rules_nodejs v2.0.0.

In v2.0.0 of the NodeJS rules, Bazel workspaces are recommended
to no longer be symlinked under a separate repository. Instead,
bazel rules and targets should be accessed directly from the
user-selected NPM repository. Usually `@npm`, so that the import
changes to `@npm//@angular/dev-infra-private/<..>`.

PR Close #37968

2020-07-13 14:18:22 -07:00

2 Commits