Patrick Staton

this probably helps ``` 2022-08-15 14:05:05.914 [ 731] [pool-3-thread-40] INFO com.hedera.hashgraph.client.core.helpers.TransactionCallableWorker.process(TransactionCallableWorker.java:88) - Submitting transaction [email protected] to sdk 2022-08-15 14:05:05.931 [ 731] [pool-3-thread-40] TRACE com.hedera.hashgraph.sdk.Executable.getNodeForExecute(Executable.java:411) - Using node 0.0.3 for request...

This is now fixed, I sent a support ticket to ken and he made the HLS stream transition to the main stream automatically like the other streams. He said he...

The code here https://github.com/nrwl/nx/blob/master/packages/react/src/executors/module-federation-dev-server/module-federation-dev-server.impl.ts#L58 assumes that the parent directory name is the same as the name of the project. That is not always the case.

In other words, if the output path for my project, which is named foo-bar, is dist/foo/bar, then the server will serve up the foo directory and try to load resources...

in the case of more than one static remote, yes. The problem is when there is only one static remote.

@Coly010 there is still a problem when the output directory does not contain the whole project name

@Coly010 The problem I see with that is that It requires a new build of all deps. I actually just ended up writing our own dev server for various reasons....

Correct. I don't think that is too bad. Certainly not as bad as a whole nx nodejs process. Maybe a more lightweight http server could be used, but express is...

Creating forked processes, yes it would do that. But multiple expressjs in the same process will not do that. I just ran this code on my machine and the node...

To be clear, in my dev server, all the epressjs instances are in the same process as the dev server.