cargdev/angular
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity

test: remove Bazel schematics integration test (#37190)

Browse Source 
This commit removes the integration test for schematics in
`@angular/bazel` that is used to generate a Bazel builder. The Bazel
builder has been deprecated.

PR Close #37190
This commit is contained in:
Keen Yee Liau
2020-05-18 16:23:14 -07:00
committed by Matias Niemelä
parent 060dcfbba1
commit a4131752d2
7 changed files with 9 additions and 8514 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
packages/bazel/src/schematics/README.md
View File

@ -2,16 +2,19 @@
Bazel builder for Angular CLI has been deprecated.
The schematics for Bazel builder have been in Angular Labs for some time,
but over the course of its evaluation the Angular team has found that they did
not meet our expectation of providing a smooth experience to get users onboard.
**tl;dr: We have deprecated the the Bazel builder and schematics for Angular CLI. As of Angular v10 we removed the ability to call `ng add @angular/bazel` to convert existing Angular CLI projects to use Bazel. We believe that some Angular projects can greatly benefit from using Bazel - these projects should use Bazel Web directly as documented in the [canonical example in the Bazel Web repo](https://github.com/bazelbuild/rules_nodejs/tree/master/examples/angular).**
The schematics for Bazel builder have been in Angular Labs for some time. Via labs we have been able to experiment with wrapping Bazel into the CLI and make it's use in the CLI invisible to developers using Angular CLI.
Through this experiment we, the Angular team have found that wrapping Bazel into Angular CLI does currently not meet our expectation of providing a great experience to developers using Angular.
There are multiple factors:
1. Bazel ecosystem for Javascript is still evolving at a rapid pace.
2. The introduction of Ivy compiler enables new ways to use Bazel in a faster
1. Bazel ecosystem for the Web is still evolving at a rapid pace.
2. The introduction of the Angular Ivy compiler enables new ways to use Bazel in a faster
and more efficient manner.
3. Feature parity with Angular CLI is difficult to achieve.
3. Feature parity with Webpack based Angular CLI is currently difficult to achieve without trade offs that would not be acceptable for many Angular users.
For users who are currently using Bazel builder, there are a few migration
options.