Trying quickstart

[lorenzo-gomez-windhover]

Hi there,

I tried the instructions on the quickstart:

git clone https://github.com/akhenry/openmct-yamcs.git
cd openmct-yamcs
npm install
npm run build:example
npm start

I'm running the yamcs quickstart.

I get the following in Chrome and Firefox:

Uncaught TypeError: openmct.telemetry.BatchingWebSocket is not a constructor
    RealtimeProvider realtime-provider.js:61
    install openmct-yamcs.js:66
    install MCT.js:421
    <anonymous> index.js:49
    <anonymous> index.js:109
    js openmct-yamcs-example.js:29
    __webpack_require__ openmct-yamcs-example.js:732
    <anonymous> openmct-yamcs-example.js:1802
    <anonymous> openmct-yamcs-example.js:1806
    webpackUniversalModuleDefinition openmct-yamcs-example.js:17
    <anonymous> openmct-yamcs-example.js:18
realtime-provider.js:61
    RealtimeProvider realtime-provider.js:61
    install openmct-yamcs.js:66
    install MCT.js:421
    <anonymous> index.js:49
    <anonymous> index.js:109
    js openmct-yamcs-example.js:29
    __webpack_require__ openmct-yamcs-example.js:732
    <anonymous> openmct-yamcs-example.js:1802
    <anonymous> openmct-yamcs-example.js:1806
    webpackUniversalModuleDefinition openmct-yamcs-example.js:17
    <anonymous> openmct-yamcs-example.js:18

Some more info:

NAME="Pop!_OS"
VERSION="20.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
LOGO=distributor-logo-pop-os

Firefox 126.0.1 (64-bit)
Chrome Version 126.0.6478.61 (Official Build) (64-bit)
Yamcs version: 16:55:08.904 _global [1] YamcsServer Yamcs 5.9.6, build b7544c20d2fae5353cf95b3e344067e7aa63bdbe

The browser page:

Thanks

[lorenzo-gomez-windhover]

Looks like this is the same issue as #427. Was able to "fix it" with npm run build:example:master

[ozyx]

Looks like this is the same issue as #427. Was able to "fix it" with npm run build:example:master

Ah! Glad you were able to solve this.