IF I am understanding the question correctly and fwiw (for what its worth) I have to agree that having to manually copy an RCL dependency, like a JS module, to the host project in order to, say, instantiate an object ostensibly provided by the RCL breaks the idea of a self-contained UI library. It's not.
For example, if the RCL provides say a "Pager" JS object and the Host JS can't do
let pager = new Pager()
The RCL then can't be packaged for NuGet installation without scripting the install (and I'm not even sure that it can be done there) and worse, arbitrarily stuffing a JS file into the host project's unknown file structure.
Supposedly static resources can be embedded into an RCL but in the case of JS, there doesn't seem to be any way to reference said resource directly from the Host's own scripts.
IMO that greatly reduces the usefulness of the RCL over say View Components or Partial Views, so....
if anyone knows how to accomplish this I'd be grateful for a post :-)