[Net\serve]: When serving with Chrome parameters, 'serve' cannot be executed until the Chrome window is closed.

[scifx]

Summary

When serving with Chrome parameters, 'serve' cannot be executed until the Chrome window is closed."

Current Behavior

The server code waits for the Chrome process to be terminated after you use Chrome parameters. Unless you manually close the browser window, the server code cannot run. This is likely due to a lack of asynchronous execution, where Chrome blocks the server code.

example:

serve.chrome [
    GET "/"
    $[][
        "hello"
    ]
]

Expected Behavior

No response

Steps To Reproduce

No response

OS

windows 11,(maybe linux?)

Version

0.10.0 Arizona Bark ,0.984 (maybe all)

Anything else?

Perhaps asynchronous support should be considered.

Is there an existing issue for this?

• I have searched the existing issues

[drkameleon]

That's a bad one... and yes, unfortunately it has to with our like of proper async.

That being said, I would suggest you have a look into Grace source code. In the main entry file (look at uiapp, etc) I did some trick to actually spawn a different process (yes, that we can do) with the serve and then load that into the webview.

It should work for you - not the "real deal" yet, but quite close! 😉