sockjs-client updated -> Incompatibile SockJS! Main site uses: "1.1.0", the iframe: "1.0.1"

[Volune]

sockjs-client has been updated two days ago to 1.1.0

When using a fresh install of webpack-dev-server, it now results in the following message in the browser: Incompatibile SockJS! Main site uses: "1.1.0", the iframe: "1.0.1" (I use npm 3.8.6)

Extract of dependencies:

`-- webpack-dev-server@1.14.1
  +-- sockjs@0.3.17
  +-- sockjs-client@1.1.0
  ...

sockjs@0.3.17 by default use sockjs-client@1.0.1 from a CDN. Maybe webpack-dev-server should pass the option sockjs_url to the SockJS server and so provide the correct version of sockjs-client without relying on a CDN ?

[codycoggins]

Experiencing same issue here.

"webpack": "^1.12.12",
"webpack-dev-server": "^1.14.1",

Running an environment based on:
https://github.com/rangle/angular2-redux-starter.git"

[Volune]

I put a fix there: https://github.com/Volune/webpack-dev-server/tree/serve-sockjs-client-v1.14.x
This is based on v1.14.1, let me know if you want a pull request on a specific branch.

[jahe]

I fixed it by overriding the dependent "sockjs-client" module with version 1.0.1 by creating a npm-shrinkwrap.json file next to the package.json with the following content:
{ "dependencies": { "webpack-dev-server": { "version": "1.14.1", "from": "webpack-dev-server@1.14.1", "dependencies": { "sockjs-client": { "version": "1.0.1", "from": "sockjs-client@1.0.1" } } } } }

This is kind of a messy solution but it solves the problem.

[SpaceK33z]

Is this still happening? If so, is there are an easy way to reproduce this?

[Volune]

@SpaceK33z Still happening, please see this gist: https://gist.github.com/Volune/a73b956b2ee911b77c3cbcad5699c85d

[SpaceK33z]

@Volune, I tested your gist. It seems like you forgot to include the webpack-dev-server client script, because the websocket does not connect. If I add --inline to the server script, everything works correctly.

[AlexGrrr]

@SpaceK33z I tried the gist with "webpack-dev-server --inline" and it throws the same error - "Incompatible SockJS! Main site uses: "1.1.1", the iframe: "1.0.1""
The iframe references a CDN script.
If you're saying it works, could you post a gist?

[SpaceK33z]

@AlexGrrr, I used that gist too, with --inline. However, it could be that SockJS falls back to another "transporting" mode then websockets. What browser do you use?

EDIT: oh wait, you're using the iframe modus. Let me test that.

[SpaceK33z]

Also tested with the iframe modus (following the steps in the gist exactly this time), but that also seems to work for me. Could you let me know what browser version and OS you're using?

[AlexGrrr]

@SpaceK33z
Thanks for getting back to me.

The OS is windows 7
I tried in many browsers with the same error -
Chrome 52
IE 11
Firefox 47