-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Moving from 4.1.3 to 4.2.0 -> xmlhttprequest-ssl' relative to engine.io-client error #1494
Comments
We used a fork of But switching version should properly resolve the dependencies, so I guess it's a problem with codesandbox? |
There are some bugs in the I have enabled CORS on the socket server as well as the express server I was stuck at this issue for hours tried everything no luck establish a WebSocket connection with the server, finally downgraded to The below code works on
Upon inspecting Network for ws connections using using when I use the |
@darrachequesne Could well be a codesandbox issue - I just did a quick hello world there, but wanted to report it in case it would be of interest to you. OTOH, I would assume that codesandbox generically just downloads packages as specified in package.json, so I'm not sure it could be buggy there and make any assumptions (in the end, it did end up with code that was referring to that SSL library). @alpha-titan Looks like your issue is not related to the one reported here? |
@alpha-titan I was not able to reproduce, could you please check https://github.com/socketio/socket.io-fiddle/tree/issues/socket.io/1494? Could you please open a new issue with all necessary details? @hardcodet I could in fact reproduce: I don't understand why though. A fresh "npm install" or "yarn add" both includes the
If someone can shed some light on this... |
@darrachequesne I have a React |
@hardcodet Yeah sorry for that I will open a new Issue |
I encountered this while upgrading to 4.2.0 in react-native environment. The metro bundler gave this error:
Doing npm ls show the package was installed:
|
It seems the core issue is that somehow the bundler is trying to resolve the package relatively from the old path (from 4.1.3). Based on the log above, it's trying to find the package in Maybe the dist generated still has the old artifact? |
Very weird - I grep through the installed code in |
@louisgv did you try to reset metro-s cache with Reference: https://facebook.github.io/metro/docs/troubleshooting |
I'm seeing a similar issue. I landed on this CodeSandbox from this article. Updating |
@darrachequesne I found this: codesandbox/codesandbox-client#4456 (comment) |
It seems vite has issues with absolute dependencies in the "browser" field, so we'll provide a quick workaround. Related: - socketio/socket.io-client#1494 - socketio/socket.io-client#1495
This should be fixed in version 4.3.1. Could you please check? |
Apologies. I ran into this in Codesandbox. I assume the only way I could check is if Codesandbox upgraded, right? Unless there is an easier way to check? |
This should be fixed by socketio/engine.io-client@4971914, included in version Please reopen if needed. |
Describe the bug
I was toying around with socket.io in codesandbox.io, and experienced a crash pretty much right away. When switching to 4.1.3, the error went away:
ModuleNotFoundError
Could not find module in path: 'xmlhttprequest-ssl' relative to '/node_modules/engine.io-client/lib/transports/index.js'
To Reproduce
Please fill the following code example:
Socket.IO server version:
x.y.z
Client (4.2.0)
The text was updated successfully, but these errors were encountered: