build: re-enable all temporary disabled e2e tests #15623
Conversation
Updates all Angular packages expect "@angular/compiler-cli" to the latest beta version. This allows us to pick up recent Bazel fixes which allow us to fully re-enable all e2e tests. Additionally we can now update to the latest `rules_nodejs` version that switched from `rollup` to `terser`. Additionally since we updated `@angular/[email protected]`, we can take advantage of angular/angular@105cfaf and move forward with using the Bazel `ng_package` output for the NPM release output.
devversion
requested review from
andrewseguin,
crisbeto,
jelbourn,
josephperrott and
mmalerba
as code owners
googlebot
added
the
cla: yes
crisbeto
added
pr: lgtm
action: merge
|
I see that you just added the If you want your PR to be merged, it has to pass all the CI checks. If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help. |
The NodeJS rule now transitively bring in the `source-map-support` dependency and therefore we don't need to add it to various Bazel targets. Also specifying the `jasmine` attribute is currently not working as it breaks the runfile dependency of `@npm//@bazel/jasmine`. `@bazel/jasmine` transitively brings its own version of `jasmine`.
devversion
added
pr: merge safe
target: patch
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
No description provided.