Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
sockjs-client updated -> Incompatibile SockJS! Main site uses: "1.1.0", the iframe: "1.0.1"
See original GitHub issuesockjs-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 ?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:10
- Comments:18 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Any chance of releasing this fix for Webpack 1?
Hot Module Replacement is still unusable in webpack dev server V1 due to this bug. Will https://github.com/webpack/webpack-dev-server/pull/493 be backported for webpack 1?