Now that npm package binaries are dynamic rules, how can I pass them in as attributes to other build rules?

[cfife-btig]

I feel like other people may have asked about the same problem but in different ways.

I am working on creating a patch file for rules_proto_grpc for their javascript grpc web library. This is necessary in order to complete our transition from

The problem I'm having is that it wants me to pass in rules that it can no longer find.

For example, before when I was using bazel_build_rules_nodejs, the tool attribute would look something like the following.

# grpc-node
proto_plugin(
    name = "grpc_node_plugin",
    empty_template = "empty.template",
    exclusions = [
        "google/protobuf",
    ],
    options = [
        "grpc_js",
    ],
    outputs = ["{protopath}_grpc_pb.js"],
    #  This works great
    tool = "@npm//grpc-tools/bin:grpc_tools_node_protoc_plugin",
    visibility = ["//visibility:public"],
)

But with rules_js, it can no longer find the the bin rule (my guess being because I would first need to load it in.

# grpc-node
proto_plugin(
    name = "grpc_node_plugin",
    empty_template = "empty.template",
    exclusions = [
        "google/protobuf",
    ],
    options = [
        "grpc_js",
    ],
    outputs = ["{protopath}_grpc_pb.js"],
    # Doesn't work and can't find it
    tool = "@npm//grpc-tools/package_json:bin.grpc_tools_node_protoc_plugin", 
    visibility = ["//visibility:public"],
)

What would be the a way to work around this?