Once this is mandatory ... I already see so many hours of my life being wasted to
a) manage it
b) trying to extend while adding libraries/projects
c) finding the bugs that were added during a) / b) ...
Does this switch to bazel also means that angular.json would be obsolete?
I tried bazel on my projects (small-ish) and it felt that angular without bazel built faster than with bazel, but it could be just some weird issues (on a mac)
Senior Developer Advocate at Microsoft ★ GDE for Google ★ Angular and Node.js contributor ★ BytecodeAlliance contributor & WebAssembly enthusiast
Does this switch to bazel also means that angular.json would be obsolete?
No, the angular.json is still mandatory. You have to keep it!
Actually, when you run ng add @angular/bazel, we update your angular.json to automatically switch from the older builder to the new Bazel builder, so you can keep running the usual ng build command. See:
Wow. Thanks for the Bazel Intro 🎉
Once this is mandatory ... I already see so many hours of my life being wasted to
a) manage it
b) trying to extend while adding libraries/projects
c) finding the bugs that were added during a) / b) ...
Does this switch to bazel also means that angular.json would be obsolete?
I tried bazel on my projects (small-ish) and it felt that angular without bazel built faster than with bazel, but it could be just some weird issues (on a mac)
No, the
angular.jsonis still mandatory. You have to keep it!Actually, when you run
ng add @angular/bazel, we update yourangular.jsonto automatically switch from the older builder to the new Bazel builder, so you can keep running the usualng buildcommand. See:github.com/bazelbuild/rules_nodejs...