Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: added clientPort to HmrOptions #3578

Merged
merged 4 commits into from
May 29, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
docs(hmr): describe the new clientPort option in server.hmr
  • Loading branch information
johnnysprinkles committed May 28, 2021
commit cfc3e1400a81e8690a2c58cb5b632c22b0bd3ad2
7 changes: 6 additions & 1 deletion docs/config/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -418,12 +418,17 @@ export default async ({ command, mode }) => {

### server.hmr

- **Type:** `boolean | { protocol?: string, host?: string, port?: number, path?: string, timeout?: number, overlay?: boolean }`
- **Type:** `boolean | { protocol?: string, host?: string, port?: number, path?: string, timeout?: number, overlay?: boolean, clientPort?: number }`

Disable or configure HMR connection (in cases where the HMR websocket must use a different address from the http server).

Set `server.hmr.overlay` to `false` to disable the server error overlay.

`clientPort` is an advanced option that overrides the port only on the client
side, allowing you to serve the websocket on a different port than the client
code looks for it on. Useful if you're using an SSL proxy in front of your dev
server.
johnnysprinkles marked this conversation as resolved.
Show resolved Hide resolved

### server.watch

- **Type:** `object`
Expand Down