Skip to content

Learners get confused by HMR websocket port #18

@kazemicode

Description

@kazemicode

Description

The Hot Module Replacement (HMR) websocket gets dynamically created on a random port in Codespaces to enable live reloads upon code changes while the app is deployed and loaded in the browser. However, we only instruct learners to set the app and API ports as public, not the dynamically created HMR port. This does not disrupt how the app and API function, but it does log an error to console saying that the connection to the websocket failed. Some students have seen this and thought they had done something wrong.

Solution

Add the flag --no-hmr to the start script. This should be done for all labs using this SPA.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions