build: allow ng_package patch to silently fail so that issue can be fixed in angular repo

[gregmagolan]

angular/angular#32603 will be fixed in angular/angular#33607 but the fix breaks this patch which breaks the material-unit-test job on that PR (https://app.circleci.com/jobs/github/angular/angular/515946). This change is temporary so that #33607 can land in angular.

[devversion]

LGTM. I assume since we now no longer use the internal/rollup but rather the package/rollup, we need to manually bring in the needed rollup plugin dependencies? Can you confirm?

Should these be actually brought in by @angular/bazel?

[gregmagolan]

Yes, these npm deps need to brought in now as they are peerDeps of @angular/bazel and no longer direct deps. We've moved a peerDeps pattern for all of the nodejs rules as it makes more sense for the node ecosystem.

Don't merge this yet, I have one last failure on angular/angular#33607 material-unit-tests to resolve: https://app.circleci.com/jobs/github/angular/angular/516209.

[devversion]

@gregmagolan I see. Thanks for the explanation. Makes sense that they are listed as peer dependencies in @angular/bazel.

[gregmagolan]

Ok. All green on the angular repo tested with this branch: https://app.circleci.com/jobs/github/angular/angular/516838

Ready to merge.

[josephperrott]

LGTM

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}