You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched for any related issues and avoided creating a duplicate issue.
Description
I'm building an app that relies on dydxprotocol link which itself relies on ws for websocket. But my app doesn't use ws explicitly so I cannot apply what's proposed on issue #1601
For example with Axios I could find a work around and feed it my proxy parameters because Axios proposes a field axios.defaults.httpsAgent.
Is there a similar parameter with ws? Or are there any trick to solve my situation?
Thanks!
ws version
8.14.2
Node.js Version
23.6.0
System
No response
Expected result
No response
Actual result
No response
Attachments
No response
The text was updated successfully, but these errors were encountered:
My hope was that by inserting the httpAgent in the beginning it would apply to all further WebSocket objects, but it doesn't work. Do you know if it's possible to make it work this way?
No, because the WebSocket instance you create is not the same created by your dependency. The dependency should allow you to pass the options to the instance that it creates. There is no other way.
Is there an existing issue for this?
Description
I'm building an app that relies on dydxprotocol link which itself relies on
ws
for websocket. But my app doesn't usews
explicitly so I cannot apply what's proposed on issue #1601For example with Axios I could find a work around and feed it my proxy parameters because Axios proposes a field
axios.defaults.httpsAgent
.Is there a similar parameter with ws? Or are there any trick to solve my situation?
Thanks!
ws version
8.14.2
Node.js Version
23.6.0
System
No response
Expected result
No response
Actual result
No response
Attachments
No response
The text was updated successfully, but these errors were encountered: