flay
flay
As per title, the RPCServer's 'upgradeAborted' event can fire after websocket upgrade was successful.
RPCClient should take an AbortSignal as a constructor option to close() on abort. This would simplify some workflows.
client.call() listens to 'abort' event from passed signal, but does not unregister after call complete This can cause a memory leak.
Only an issue in strict mode, but may cause havoc with bundlers. This should be changed to something else.
Add option to prevent queueing of calls while in CONNECTING state, or possibly allow calls to timeout while in this queue. Otherwise, it's possible for a large volume of calls...
Section 7.1 of the OCPP2.0.1J specification describes a "signed message format" which extends the RPC framework. Support for this could be added with an option to the `client.call()` method. e.g....
[Valibot](https://valibot.dev/) is a schema library very similar to zod; It offers similar functionality and a similar API. The big downside to zod (which has led to this suggestion) is that...
This addresses issue #305 It performs a safety check to ensure that the undocumented/private method `_getActiveHandles` exists on the process object before calling it. I had thought about using the...
The `autoExitHook` method of the `IPCTransport` class calls an __undocumented method__ of the node.js `process` class, namely `_getActiveHandles`. This method does not exist in the process class of Deno 2,...