-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
SockJS-Client version mismatch #1268
Comments
I’m a bit confused, why do you
? This is a bit hidden so I don’t quite understand your use case. |
Sorry I was unclear. Browsing to the iframe.html is just a way of seeing the version mismatch for yourself (if websockets fail SockJS-Client attaches an iframe pointing at that url, but as websockets probably work for you then browsing to that url and viewing source will let you see the 1.0.1 vs 1.0.3 version mismatch). You can reproduce the error yourself by disabling websockets in your browser, and then on the very first page that appears after running
My use case is trying to integrate create-react-app with a CMS. During development I'm proxying the dev server from the CMS, but the CMS platform can't proxy websockets and I get this error which prevents me getting SockJS features such as reloads. |
Could you submit a fix please if you have one in mind? |
I experienced the same problem while I set project myself, and I found out downgrading webpack-dev-server will do the job. In my case, I used webpack 1.12.9, webpack-dev-server 1.12.0. Previously I just use latest (both). |
This was presumably fixed by #1274, released in 0.9.0. Please verify and let us know! |
If you start the dev server and browse to,
You'll see the fallback for when a browser can't establish a websocket connection. It references a CDN version of SockJS-Client 1.0.1
But the chosen SockJS-Client version elsewhere in
react-dev-tools
is 1.0.3 so it fails with this error,SockJS-Client 1.0.3 was chosen at https://github.com/facebookincubator/create-react-app/blob/master/packages/react-dev-utils/package.json#L31
If you disable websockets in your browser, or have a proxy that doesn't handle websockets (like I do), you can reproduce this error.
You could fix this by downgrading the package.json to version 1.0.1, or by using a fork of sockjs-node that matches the version you want by applying this patch holloway/sockjs-node@6c1a7b6
Incidentally the current version of SockJS-Client is 1.1.1.
The text was updated successfully, but these errors were encountered: