-
Notifications
You must be signed in to change notification settings - Fork 94
ts_proto_library cannot be used by ng_package #211
Comments
Oops yeah, we made the output of ts_proto_library conform to a subset of the providers you get from a ts_library, expecting it to be used only in ts_library - Greg we already have some helper like |
I took at look at this issue and its non-trivial to fix as ng_package is expecting a Work-around for now could be to not generate Need to work with @alexeagle to figure out how to fix this properly so that we can get |
@gregmagolan Sure I can give that a go, however im not really sure how to do it. |
@Toxicable I can make the change to rules_typescript to fix the build in the case of a TS provider not providing a |
@gregmagolan I think that would be good to at least unblock this issue for now. |
angular/angular#25605 will unblock this issue. Once that lands you'll also need
in your |
angular/angular#25648 landed on the 6.1.x branch. still waiting to land angular/angular#25605 on master. |
Everything merged into to both master & the 6.1.x branch. |
This error is throw when using ts_proto_library as a dep on a ng_module that is being used by a ng_package.
The ng_module works fine but when it goes into ng_package it breaks.
ts_proto_library -> ng_module -> ng_package
reproduction here: angular/universal#1003
bazel build modules/grpc-engine:npm_package
The text was updated successfully, but these errors were encountered: