-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebsocketTransportClient is not a constructor #254
Comments
Hi @mattydono Could you please provide a reproduction example? I wasn't able to reproduce this through a simple example/test. Please see: https://github.com/viglucci/rsocket-js-websocket-example Based on your screenshot, I suspect you are trying to use RSocket-js in a client-side application. Are you using Webpack, Vite, or another bundler? |
Thanks for that additional info. Can you answer this question:
RSocket used to provide an alternative implementation of Buffer, however this is no longer the case in v1.X. This article may help: https://viglucci.io/articles/how-to-polyfill-buffer-with-webpack-5 You can also reference the WebPack example:
|
I'm using vite, reading into the above |
Concerning vite, you may also wish to reference this previous issue: #195 (comment) |
Hey @mattydono were you able to find a solution here? If so I would like to close out this issue. |
Closing this out as haven't heard back from Author. |
Expected Behavior
instantiate a new WebsocketClientTransport class with constructor args of ClientOptions
Actual Behavior
WebsocketClientTransport registers a type error
Steps to Reproduce
packages:
attempt to instantiate new WebsocketClientTransport class
The text was updated successfully, but these errors were encountered: