Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: webpack/webpack-dev-server
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v5.2.4
Choose a base ref
...
head repository: webpack/webpack-dev-server
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v5.2.5
Choose a head ref
  • 4 commits
  • 17 files changed
  • 4 contributors

Commits on May 25, 2026

  1. fix: skip HMR websocket path when forwarding upgrades to user-defined…

    … proxies (#4316)
    
    * fix: never proxy hot-reload websocket requests
    
    Both create-react-app and vue-cli-service have introduced workarounds for this, but it seems to me that this is always desirable behaviour for webpack-dev-server.
    
    vuejs/vue-cli@72ba750
    react/create-react-app#7444
    
    * test: update snapshot and proxy option tests for port 8162
    
    * fixup!
    
    ---------
    
    Co-authored-by: Sebastian Beltran <[email protected]>
    ajhyndman and bjohansebas authored May 25, 2026
    Configuration menu
    Copy the full SHA
    93e8996 View commit details
    Browse the repository at this point in the history

Commits on Jun 12, 2026

  1. fix(proxy): match the HMR upgrade path exactly like the ws server (#5678

    )
    
    * test(proxy-option): extend HMR upgrade coverage to URL variants of the configured path
    
    Adds trailing slash, case variations, percent-encoded path, and
    leading double slash to the existing HMR/proxy isolation tests so
    that all URL shapes recognized as the HMR upgrade are treated
    consistently.
    
    * fix(proxy): normalize HMR upgrade path comparison
    
    Tighten the HMR-vs-proxy upgrade dispatch so URL variants of the
    configured HMR path are consistently recognized as the HMR socket:
    
      - lowercase comparison (case-insensitive)
      - decode percent-encoding before comparison
      - strip trailing slashes
      - collapse leading multiple slashes so //foo is treated as /foo
        instead of being parsed as a scheme-relative URL
      - wrap URL parsing in try/catch so a malformed req.url does not
        raise an uncaught exception
    
    * fix(proxy): enforce exact HMR upgrade path matching for websocket connections
    
    * fix(proxy): improve HMR upgrade path handling and user proxy integration
    
    * ci: pin node 24
    
    * fix(test): update Node.js version matrix and adjust test naming for clarity
    
    * fix(proxy): enhance HMR upgrade handling by improving WebSocket server management
    
    ---------
    
    Co-authored-by: Sebastian Beltran <[email protected]>
    UlisesGascon and bjohansebas authored Jun 12, 2026
    Configuration menu
    Copy the full SHA
    948d5e6 View commit details
    Browse the repository at this point in the history
  2. feat: add changeset validation and release workflow (#5680)

    * feat: add changeset validation and release workflow
    
    * fixup!
    bjohansebas authored Jun 12, 2026
    Configuration menu
    Copy the full SHA
    60173be View commit details
    Browse the repository at this point in the history
  3. chore(release): new release (#5682)

    Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
    github-actions[bot] authored Jun 12, 2026
    Configuration menu
    Copy the full SHA
    c3ee325 View commit details
    Browse the repository at this point in the history
Loading