We currently consume runtime.<RID>.Microsoft.NETCore.Runtime.Wasm.Node.Transport in the runtime repo. This package is built in dotnet/node, while we also have Microsoft.NET.Runtime.Emscripten.5.0.6.Node.<RID> which we actually ship. The only difference is the latter is missing npm.
We should create an internal/transport package that includes npm in the emsdk repo since that would simplify the flow (right now we need to have a kind of weird node -> VMR subscription for CoherentParentDependency between runtime/emsdk).
We currently consume
runtime.<RID>.Microsoft.NETCore.Runtime.Wasm.Node.Transportin the runtime repo. This package is built in dotnet/node, while we also haveMicrosoft.NET.Runtime.Emscripten.5.0.6.Node.<RID>which we actually ship. The only difference is the latter is missing npm.We should create an internal/transport package that includes npm in the emsdk repo since that would simplify the flow (right now we need to have a kind of weird node -> VMR subscription for CoherentParentDependency between runtime/emsdk).