JeremyTCD

Hey no problem. Yes, communication between the .Net and Node.js processes occurs over HTTP. The library only supports HTTP. Just to clarify, could you elaborate on > corporate proxies are...

Hey! Not with this library unfortunately. Just a shot in the dark - might switching to HTTPS help? Since TCP proxies cannot read/edit content over HTTPS, the proxies might ignore...

We could do with something like webpack's [aggregateTimeout](https://webpack.js.org/configuration/watch/#watchoptionsaggregatetimeout) option: "Add a delay before rebuilding once the first file changed. This allows webpack to aggregate any other changes made during this...

Hey apologies for the slow response, I'm not sure how to pipe output when using JavaScriptEngineSwitcher, but if you use this library directly, you can do it like this: ```cs...

Ah it does not. I assumed from your "hi" example that you just needed output, stdin is not piped from .Net to Node.js. Would an invocation work? E.g. ```cs string?...

Options: - Use invocations to "pipe" input to the Node.js process. - Register a custom service for [INodeJSProcessFactory](https://github.com/JeringTech/Javascript.NodeJS/blob/master/src/NodeJS/NodeJSServiceImplementations/OutOfProcess/INodeJSProcessFactory.cs) that pipes input to the Node.js process.

Piping input to Node.js processes is not supported out-of-the-box. But there are ways to implement such behaviour. For the first option, read input and pass it to the Node.js process...

``` {"status":"failed","failures":1,"message":"Could not find Cypress test run results"} ``` This means this library is working, you'll need to look into your Cypress setup.

Could you reproduce the error with debug logging enabled?

@CallumVass Thanks for the details. We did make changes from beta 4 to 5 that affected script length: - Moved from webpack to vite. Webpack was minifying the script, vite...