build issue

Following error when compiling frontend

ERROR in ./src/app/devices/device-editor/device-editor.component.ts
Module not found: Error: Can't resolve '@aspnet/signalr-client' in 'C:\repos\git\Bing-Maps-Fleet-Tracker\Frontend\src\app\devices\device-editor'
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device-editor/device-editor.component.ts (9,31): Cannot find module '@aspnet/signalr-client'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (31,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (61,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (64,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (67,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (71,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (72,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (73,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (74,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (75,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (78,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (82,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (15,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (17,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (31,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (33,7): Cannot find name 'spyOn'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (36,7): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (39,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (41,7): Cannot find name 'spyOn'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (43,7): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (46,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (48,7): Cannot find name 'spyOn'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (50,7): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (53,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (55,7): Cannot find name 'spyOn'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/assets/asset.service.spec.ts (57,7): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/data.service.spec.ts (9,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/data.service.spec.ts (10,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/settings.service.spec.ts (8,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/settings.service.spec.ts (9,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/settings.service.spec.ts (15,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/settings.service.spec.ts (16,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/nav/nav.component.spec.ts (11,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/nav/nav.component.spec.ts (15,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/nav/nav.component.spec.ts (22,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/nav/nav.component.spec.ts (28,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/nav/nav.component.spec.ts (29,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/settings/settings.component.spec.ts (8,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/settings/settings.component.spec.ts (12,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/settings/settings.component.spec.ts (19,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/settings/settings.component.spec.ts (25,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/core/settings/settings.component.spec.ts (26,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (14,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (15,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (27,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (29,7): Cannot find name 'spyOn'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (32,7): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (35,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (37,7): Cannot find name 'spyOn'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (39,7): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (42,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (44,7): Cannot find name 'spyOn'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (46,7): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (49,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (51,7): Cannot find name 'spyOn'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device.service.spec.ts (54,7): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching.service.spec.ts (8,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching.service.spec.ts (9,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching.service.spec.ts (15,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching.service.spec.ts (16,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching-editor/dispatching-editor.component.spec.ts (8,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching-editor/dispatching-editor.component.spec.ts (12,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching-editor/dispatching-editor.component.spec.ts (19,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching-editor/dispatching-editor.component.spec.ts (25,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching-editor/dispatching-editor.component.spec.ts (26,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching-show/dispatching-show.component.spec.ts (8,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching-show/dispatching-show.component.spec.ts (12,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching-show/dispatching-show.component.spec.ts (19,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching-show/dispatching-show.component.spec.ts (25,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/dispatching-show/dispatching-show.component.spec.ts (26,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/location-dialog/location-dialog.component.spec.ts (8,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/location-dialog/location-dialog.component.spec.ts (12,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/location-dialog/location-dialog.component.spec.ts (19,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/location-dialog/location-dialog.component.spec.ts (25,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/dispatching/location-dialog/location-dialog.component.spec.ts (26,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/locations/location.service.spec.ts (8,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/locations/location.service.spec.ts (9,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/locations/location.service.spec.ts (15,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/locations/location.service.spec.ts (16,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/locations/location-list/location-list.component.spec.ts (8,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/app.component.spec.ts (27,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/locations/location-list/location-list.component.spec.ts (19,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/locations/location-list/location-list.component.spec.ts (25,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/locations/location-list/location-list.component.spec.ts (26,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/maps/maps/maps.component.spec.ts (15,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/maps/maps/maps.component.spec.ts (20,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/maps/maps/maps.component.spec.ts (36,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/maps/maps/maps.component.spec.ts (42,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/maps/maps/maps.component.spec.ts (43,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/filter-list.pipe.spec.ts (6,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/filter-list.pipe.spec.ts (7,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/filter-list.pipe.spec.ts (9,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/filter-list.pipe.spec.ts (12,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/filter-list.pipe.spec.ts (14,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/time-filter/time-filter.component.spec.ts (11,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/time-filter/time-filter.component.spec.ts (15,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/time-filter/time-filter.component.spec.ts (22,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/time-filter/time-filter.component.spec.ts (28,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/time-filter/time-filter.component.spec.ts (29,5): Cannot find name 'expect'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/trip-list/trip-list.component.spec.ts (11,1): Cannot find name 'describe'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/trip-list/trip-list.component.spec.ts (15,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/trip-list/trip-list.component.spec.ts (22,3): Cannot find name 'beforeEach'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/trip-list/trip-list.component.spec.ts (28,3): Cannot find name 'it'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/shared/trip-list/trip-list.component.spec.ts (29,5): Cannot find name 'expect'.
ERROR in<EMAIL_ADDRESS>(142,47): ';' expected.
ERROR in<EMAIL_ADDRESS>(142,90): '(' expected.
ERROR in<EMAIL_ADDRESS>(142,104): ']' expected.
ERROR in<EMAIL_ADDRESS>(142,112): ',' expected.
ERROR in<EMAIL_ADDRESS>(142,113): Property assignment expected.
ERROR in<EMAIL_ADDRESS>(142,121): ')' expected.
ERROR in<EMAIL_ADDRESS>(142,147): '(' expected.
ERROR in<EMAIL_ADDRESS>(142,162): ']' expected.
ERROR in<EMAIL_ADDRESS>(142,163): ',' expected.
ERROR in<EMAIL_ADDRESS>(142,164): Property assignment expected.
ERROR in<EMAIL_ADDRESS>(142,165): Property assignment expected.
ERROR in<EMAIL_ADDRESS>(142,179): ',' expected.
ERROR in<EMAIL_ADDRESS>(142,183): ':' expected.
ERROR in<EMAIL_ADDRESS>(142,208): '{' expected.
ERROR in<EMAIL_ADDRESS>(142,217): ':' expected.
ERROR in<EMAIL_ADDRESS>(142,222): ',' expected.
ERROR in<EMAIL_ADDRESS>(142,227): ':' expected.
ERROR in<EMAIL_ADDRESS>(142,228): Expression expected.
ERROR in<EMAIL_ADDRESS>(142,230): ')' expected.
ERROR in<EMAIL_ADDRESS>(635,30): ';' expected.
ERROR in<EMAIL_ADDRESS>(720,1): Declaration or statement expected.
ERROR in<EMAIL_ADDRESS>(142,224): An object literal cannot have multiple properties with the same name in strict mode.
ERROR in<EMAIL_ADDRESS>(575,13): Invalid use of 'arguments'. Modules are automatically in strict mode.
ERROR in<EMAIL_ADDRESS>(142,68): 'ReadonlyArray' only refers to a type, but is being used as a value here.
ERROR in<EMAIL_ADDRESS>(142,92): The right-hand side of an arithmetic operation must be of type 'any', 'number' or an enum type.
ERROR in<EMAIL_ADDRESS>(142,94): Cannot find name 'methodName'.
ERROR in<EMAIL_ADDRESS>(142,106): Cannot find name 'string'.
ERROR in<EMAIL_ADDRESS>(142,124): 'ReadonlyArray' only refers to a type, but is being used as a value here.
ERROR in<EMAIL_ADDRESS>(142,149): The right-hand side of an arithmetic operation must be of type 'any', 'number' or an enum type.
ERROR in<EMAIL_ADDRESS>(142,150): A computed property name must be of type 'string', 'number', 'symbol', or 'any'.
ERROR in<EMAIL_ADDRESS>(142,151): Cannot find name 'P'.
ERROR in<EMAIL_ADDRESS>(142,156): Cannot find name 'keyof'.
ERROR in<EMAIL_ADDRESS>(142,162): Cannot find name 'T'.
ERROR in<EMAIL_ADDRESS>(142,180): Cannot find name 'P'.
ERROR in<EMAIL_ADDRESS>(142,217): Cannot find name 'T'.
ERROR in<EMAIL_ADDRESS>(142,219): Cannot find name 'P'.
ERROR in<EMAIL_ADDRESS>(635,49): Cannot find name 'T'.
ERROR in<EMAIL_ADDRESS>(635,51): Cannot find name 'k'.
ERROR in<EMAIL_ADDRESS>(635,56): 'Spy' only refers to a type, but is being used as a value here.
ERROR in<EMAIL_ADDRESS>(635,62): Cannot find name 'T'.
ERROR in<EMAIL_ADDRESS>(635,64): Cannot find name 'k'.
ERROR in<EMAIL_ADDRESS>(642,24): Cannot find name 'Spy'.
ERROR in<EMAIL_ADDRESS>(644,32): Cannot find name 'Spy'.
ERROR in<EMAIL_ADDRESS>(646,41): Cannot find name 'Spy'.
ERROR in<EMAIL_ADDRESS>(648,33): Cannot find name 'Spy'.
ERROR in<EMAIL_ADDRESS>(650,34): Cannot find name 'Spy'.
ERROR in<EMAIL_ADDRESS>(652,17): Cannot find name 'Spy'.
ERROR in<EMAIL_ADDRESS>(691,37): Cannot find name 'Reporter'.
ERROR in<EMAIL_ADDRESS>(697,21): Cannot find name 'RunDetails'.
ERROR in<EMAIL_ADDRESS>(701,19): Cannot find name 'Suite'.
ERROR in<EMAIL_ADDRESS>(702,33): Cannot find name 'SuiteOrSpec'.
ERROR in<EMAIL_ADDRESS>(711,15): Cannot find name 'Spec'.
ERROR in<EMAIL_ADDRESS>(712,16): Cannot find name 'Clock'.
ERROR in<EMAIL_ADDRESS>(716,30): Cannot find name 'HtmlReporter'.
ERROR in<EMAIL_ADDRESS>(717,32): Cannot find name 'HtmlSpecFilter'.
ERROR in<EMAIL_ADDRESS>(725,26): Namespace<EMAIL_ADDRESS>has no exported member 'Jasmine'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/devices/device-editor/device-editor.component.ts (9,31): Cannot find module '@aspnet/signalr-client'.
ERROR in C:/repos/git/Bing-Maps-Fleet-Tracker/Frontend/src/app/locations/location-list/location-list.component.spec.ts (12,3): Cannot find name 'beforeEach'.

webpack: Failed to compile.

See following error on npm install, is there a way to install deprecated client?

PS C:\repos\git\Bing-Maps-Fleet-Tracker\Frontend> npm install @aspnet/signalr-client
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated, please use @aspnet/signalr instead

><EMAIL_ADDRESS>install C:\repos\git\Bing-Maps-Fleet-Tracker\Frontend\node_modules\@aspnet\signalr-client
> echo "This package has been deprecated. Use '@aspnet/signalr' instead." && exit 1

"This package has been deprecated. Use '@aspnet/signalr' instead."

PS C:\repos\git\Bing-Maps-Fleet-Tracker\Frontend> ng -v
Your global Angular CLI version (8.1.2) is greater than your local
version (1.7.4). The local Angular CLI version is used.

Had to update signal-r client library to @aspnet/signalr
Fix hubconnection to use new HubConnectionBuilder.

device-editor.component.ts (74):
const signalR = require("@aspnet/signalr");

this.hubConnection = new signalR.HubConnectionBuilder().withUrl(this.deviceService.getDeviceAdditionNotificationUrl()).build();


UX enhancement

Choose status task and it auto update if it changes from original, no need click Save button.
Edit task content and Enter => Auto detect difference and save update.
When add new task, we don't have status field.

Fixed task content and status
Default status is None when add new task

Default status is None when add new task

Need a status field when adding like priority field


Is it possible to get a js library(file) for ShellJS

Hi
I wanted to include ShellJs in my project, i wanted to know if it is possible to get JS file for the shellJS library. Is it possible to include it just as a js file or will it be bundled along with nodejs?

I'm a bit confused by the question. We support installing shelljs via npm.
You won't be able to get very far using shelljs without node. We rely on tons of node APIs (fs, os, etc.).

Thanks for the quick reply


Stream out docker-build cmd stdout

Stream out docker-build cmd stdout
Description of changes:
For more information on contributing, please see Contributing
section of our documentation.
Status

WIP

Checklist (tick everything that applies)

[ ] PreCommitChecks - Code linting (required)
[ ] Tests

Lgtm

Unit test fsiling please fix

Unit test fsiling please fix

i think im ready

@liorsav i think im ready


React player HTML append to any div

Hi,
I am usgin React Music player, Right now player creates its html into body. is it possible that we can append player html into any sections/div rather then body.
I've used bounds property, but its not working.
bounds: document.getElementById('root'),
Here it the reference:
https://www.screencast.com/t/ESDG2mZk3s7Z
Thanks in advance.

ok i'm publish a new version later .  add a option getContainer   support custom append root node

In previous version it was working fine, wherever i place  markup <ReactJkMusicPlayer  {...item.options} /> it render html on that node.

i'm sorry . i use import { createPortal } from "react-dom"; in 4.3.7 version to append document.body
because It will reduce some bugs

Hi~ Please reinstall<EMAIL_ADDRESS>use like this
<ReactJkMusicPlayer  getContainer={()=> document.body}/>

// or

<ReactJkMusicPlayer  getContainer={()=> document.querySelector('.element')}/>

Hi~ Please reinstall<EMAIL_ADDRESS>use like this
<ReactJkMusicPlayer  getContainer={()=> document.body}/>

// or

<ReactJkMusicPlayer  getContainer={()=> document.querySelector('.element')}/>

Use like this?
<ReactJkMusicPlayer getContainer={()=> document.querySelector('.audio-wrapper')} {...item.options} />

Options will remains same as it is?
<ReactJkMusicPlayer getContainer={()=> document.querySelector('.audio-wrapper')} {...item.options} />

yes no problem . cannot work ?

oh sorry it works, but it does not shows timers, or seekbar and player options are not working
Reference: https://www.screencast.com/t/XqqVOzNuA

Let me explain the complete scenario.
I've two player on my view and its rendering through .map function, every player have its own options, that's why i used item.options to assign every player its own options. there is no error in audio play. audio is playaing very well, but the options like seekbar not moving on audio play.  timer not working.
Reference : https://www.screencast.com/t/McjkwkEFs5
here is the code:
const renderMessage = (voiceMails) => {
    return voiceMails.map((item, index) => {

         item.options = {
            className: "audio-player",
            defaultPlayIndex: 0,
            theme: "light",
            glassBg: false,
            defaultPosition: {},
            openText: "Open",
            closeText: "Close",
            mode: "full",
            once: true,
            autoPlay: false,
            toggleMode: false,
            showMiniModeCover: false,
            showMiniProcessBar: false,
            drag: true,
            seeked: true,
            showProgressLoadBar: false,
            showPlay: true,
            showReload: false,
            showDownload: false,
            showPlayMode: false,
            showThemeSwitch: true,
            showLyric: false,
            extendsContent: [],
            defaultVolume: 100,
            onAudioEnded(audioInfo) {
                //console.log("audio ended", audioInfo);
                readHandler(item.fromNumber, item.recordingSid)
            },
            onAudioSeeked(audioInfo) {
                console.log("audio seeked", audioInfo);
            },
            audioLists: [
                {
                    musicSrc: () => {
                        return Promise.resolve(item.recordingMp3Uri)
                    }

                },
            ]
        };

        return (

                        <ReactJkMusicPlayer  {...item.options} onAudioLoadError={(error)=> console.log(error)}  getContainer={()=> document.querySelector('#player-' + index)} />

        )
    })
}

@lijinke666  any solution.


Easier way to specify histogram boundaries?

NB: Before opening a feature request against this repo, consider whether the feature should/could be implemented in the other OpenTelemetry client libraries. If so, please open an issue on opentelemetry-specification first.
Is your feature request related to a problem? Please describe.
It's currently somewhat unergonomic to create a histogram with custom buckets/boundaries. Because this must be done with Views, and because Views can only be provided when a MeterProvider is created, this means that the boundary configuration for a histogram must live in a completely separate part of the codebase from the createHistogram call itself. In most cases I can imagine, the buckets for a given histogram are going to be tightly coupled to what individual histograms are measuring. For example, the boundaries for a histogram tracking SQL query duration are likely to be very different from the boundaries for a histogram tracking average response size, and in both cases I'd like to specify those boundaries when I'm creating the histogram metric.
Describe the solution you'd like
I'd like to be able to define a histogram's boundaries when I call createHistogram.
Per #2999, it looks like this used to be supported by the API, though I understand that this was removed in favor of using a View.
If a View is the way to go, perhaps it would be possible to provide a View in the call to createHistogram? Maybe something like this:
meter.createHistogram('foo.duration', {
  view: new View({
    aggregation: new ExplicitBucketHistogramAggregation([0, 1, 5, 10, 15, 20, 25, 30]),
  }),
});

Alternatively, one could directly provide an aggregation and a View would be transparently create for the metric:
meter.createHistogram('foo.duration', {
  aggregation: new ExplicitBucketHistogramAggregation([0, 1, 5, 10, 15, 20, 25, 30]),
});

Describe alternatives you've considered
AFAICT, there aren't any currently viable alternatives to creating a View alongside a MeterProvider
Additional context
This feature would make it possible to easily share and reuse histogram metrics via libraries. This would be really useful for e.g. building a library that can capture common Node metrics, including a histogram for GC duration with bucket sizes that have a sensible default. I'm thinking about something akin to this from the Prometheus world: https://github.com/siimon/prom-client/blob/8d6456c05f0708fed34628da5bd6f492a0ab43f8/lib/metrics/gc.js.

You might find this spec proposal interesting:
https://github.com/open-telemetry/opentelemetry-specification/pull/3216

Сan someone tell me how to at least somehow set buckets for histogram now?

You need to define a View for it before the instruments are created

new View({
aggregation: new ExplicitBucketHistogramAggregation([1,5,10,25], true),
instrumentName: metricName,
instrumentType: InstrumentType.HISTOGRAM,
})

in unit test i found other way to achieve it

Hmm, I think I had this suggestion working and now it's stopped.  Is the metricName required? I thought I read that for instance just a units label would be enough. (eg, bytes versus ms)