You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v3, there seems to be a sockjs-client version mismatch between the version that gets bundled into into the /client directory and the version that gets installed as a dependency.
A fresh install of webpack-dev-server v3.11.3 bundles version 1.5.0 of sockjs-client into the /client directory to be used when falling back to iframe transports. However, the latest version of sockjs-client matching webpack-dev-server's dependency version constraint is currently 1.6.0 so it get installed into the main application.
This version mismatch results in the following message when iframe transports are used: Incompatibile SockJS! Main site uses: "1.6.0", the iframe: "1.5.0"
Extract from my yarn.lock:
webpack-dev-server@3.11.3:
dependencies:
sockjs-client "^1.5.0"
sockjs-client@^1.5.0:
version "1.6.0"
Actual Behavior
The following message is shown when iframe transports are used: Incompatibile SockJS! Main site uses: "1.6.0", the iframe: "1.5.0"
Expected Behavior
The version bundled into /client should match the dependency version constraint, thus avoiding the version mismatch.
How Do We Reproduce?
I ran into this when running E2E tests with Testcafe using headless Chrome. Unfortunately, I can't share the project and can't think of another easy way to reproduce this.
Please paste the results of npx webpack-cli info here, and mention other relevant information
sockjs-client1.6.0 introduce a breaking change (required Node.js 12), for backward compatible webpack-dev-server v3 should set tilde ranges~1.5.0 for sockjs-client
Bug report
In v3, there seems to be a sockjs-client version mismatch between the version that gets bundled into into the
/client
directory and the version that gets installed as a dependency.A fresh install of webpack-dev-server v3.11.3 bundles version 1.5.0 of sockjs-client into the
/client
directory to be used when falling back to iframe transports. However, the latest version of sockjs-client matching webpack-dev-server's dependency version constraint is currently 1.6.0 so it get installed into the main application.This version mismatch results in the following message when iframe transports are used:
Incompatibile SockJS! Main site uses: "1.6.0", the iframe: "1.5.0"
Extract from my
yarn.lock
:Actual Behavior
The following message is shown when iframe transports are used:
Incompatibile SockJS! Main site uses: "1.6.0", the iframe: "1.5.0"
Expected Behavior
The version bundled into
/client
should match the dependency version constraint, thus avoiding the version mismatch.How Do We Reproduce?
I ran into this when running E2E tests with Testcafe using headless Chrome. Unfortunately, I can't share the project and can't think of another easy way to reproduce this.
Please paste the results of
npx webpack-cli info
here, and mention other relevant informationSee also #474 (comment)
The text was updated successfully, but these errors were encountered: