Use the correct port when PORT is not set (#723)

jaredpalmer · Aug 18, 2018 · d7c8ece · d7c8ece
1 parent 68eead7
commit d7c8ece
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/packages/razzle-dev-utils/webpackHotDevClient.js b/packages/razzle-dev-utils/webpackHotDevClient.js
@@ -27,7 +27,7 @@ ErrorOverlay.startReportingRuntimeErrors({
  launchEditorEndpoint: url.format({
  protocol: window.location.protocol,
  hostname: window.location.hostname,
- port: parseInt(process.env.PORT, 10) + 1 || window.location.port,
+ port: parseInt(process.env.PORT || window.location.port, 10) + 1,
  pathname: launchEditorEndpoint,
  }),
  onError: function() {
@@ -48,7 +48,7 @@ var connection = new SockJS(
  url.format({
  protocol: window.location.protocol,
  hostname: window.location.hostname,
- port: parseInt(process.env.PORT, 10) + 1 || window.location.port,
+ port: parseInt(process.env.PORT || window.location.port, 10) + 1,
  // Hardcoded in WebpackDevServer
  pathname: '/sockjs-node',
  })