Unable to reach the server. Browser shows only "Cannot GET /"

Unable to reach the server. Browser shows only "Cannot GET /" when running the "yarn dev" command in the terminal

PS C:\Users\Me\Desktop\SDWAN KIT\nucleus-master> yarn dev
yarn run v1.22.4
$ concurrently --raw "npm run start:fe" "npm run start:server:dev" "npm run start:static"

> nucleus-server@1.1.3 start:fe C:\Users\Me\Desktop\SDWAN KIT\nucleus-master
> webpack-dev-server --progress --profile --colors --quiet --open

> nucleus-server@1.1.3 start:server:dev C:\Users\Me\Desktop\SDWAN KIT\nucleus-master
> nodemon --watch src --exec "npm run build:server && cross-env DEBUG=nucleus* npm run start:server:prod" -e ts

> nucleus-server@1.1.3 start:static C:\Users\Me\Desktop\SDWAN KIT\nucleus-master
> make-dir .files && serve .files --port 9999 --silent

[nodemon] 1.12.1
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: C:\Users\Me\Desktop\SDWAN KIT\nucleus-master\src/**/*
[nodemon] starting `npm run build:server && cross-env DEBUG=nucleus* npm run start:server:prod`

> nucleus-server@1.1.3 build:server C:\Users\Me\Desktop\SDWAN KIT\nucleus-master
> tsc && rm -rf lib/__spec__ lib/**/__spec__

10% building modules 5/10 modules 5 active ...\webpack-dev-server\client\overlay.js
[at-loader] Using typescript@3.1.6 from typescript and "tsconfig.json" from C:\Users\Me\Desktop\SDWAN KIT\nucleus-master\tsconfig.public.json.

'rm' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! nucleus-server@1.1.3 build:server: `tsc && rm -rf lib/__spec__ lib/**/__spec__`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nucleus-server@1.1.3 build:server script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Me\AppData\Roaming\npm-cache\_logs\2020-04-14T22_55_23_664Z-debug.log
[nodemon] app crashed - waiting for file changes befor58006ms building modules
26ms sealing
2ms optimizing
1ms basic module optimization
11ms module optimization
1ms advanced module optimization
0ms basic chunk optimization
1ms chunk optimization
1ms advanced chunk optimization
1ms module and chunk tree optimization
30ms module reviving
2ms module order optimization
13ms module id optimization
12ms chunk reviving
1ms chunk order optimization
7ms chunk id optimization
51ms hashing
3ms module assets processing
1846ms chunk assets processing
4ms additional chunk assets processing
1ms additional asset processing
1ms chunk asset optimization
91ms asset optimization
Terminate batch job (Y/N)? Terminate batch job (Y/N)? Terminate batch job (Y/N)? Terminate batch job (Y/N)? Y
PS C:\Users\Me\Desktop\SDWAN KIT\nucleus-master>
PS C:\Users\Me\Desktop\SDWAN KIT\nucleus-master>
PS C:\Users\Me\Desktop\SDWAN KIT\nucleus-master> cp config.template.js config.js
PS C:\Users\Me\Desktop\SDWAN KIT\nucleus-master>
PS C:\Users\Me\Desktop\SDWAN KIT\nucleus-master>
PS C:\Users\Me\Desktop\SDWAN KIT\nucleus-master>
PS C:\Users\Me\Desktop\SDWAN KIT\nucleus-master> yarn dev
yarn run v1.22.4
$ concurrently --raw "npm run start:fe" "npm run start:server:dev" "npm run start:static"

┌───────────────────────────────────────────────────────────────┐
│ npm update check failed │
│ Try running with sudo or get access │
│ to the local update config store via │
│ sudo chown -R $USER:$(id -gn $USER) C:\Users\Me\.config │
└───────────────────────────────────────────────────────────────┘

> nucleus-server@1.1.3 start:static C:\Users\Me\Desktop\SDWAN KIT\nucleus-master
> make-dir .files && serve .files --port 9999 --silent

> nucleus-server@1.1.3 start:server:dev C:\Users\Me\Desktop\SDWAN KIT\nucleus-master
> nodemon --watch src --exec "npm run build:server && cross-env DEBUG=nucleus* npm run start:server:prod" -e ts

> nucleus-server@1.1.3 start:fe C:\Users\Me\Desktop\SDWAN KIT\nucleus-master
> webpack-dev-server --progress --profile --colors --quiet --open

[nodemon] 1.12.1
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: C:\Users\Me\Desktop\SDWAN KIT\nucleus-master\src/**/*
[nodemon] starting `npm run build:server && cross-env DEBUG=nucleus* npm run start:server:prod`

> nucleus-server@1.1.3 build:server C:\Users\Me\Desktop\SDWAN KIT\nucleus-master
> tsc && rm -rf lib/__spec__ lib/**/__spec__

10% building modules 5/10 modules 5 active ...\webpack-dev-server\client\overlay.js
[at-loader] Using typescript@3.1.6 from typescript and "tsconfig.json" from C:\Users\Me\Desktop\SDWAN KIT\nucleus-master\tsconfig.public.json.
10% building modules 6/10 modules 4 active ...\webpack-dev-server\client\overlay.js'rm' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! nucleus-server@1.1.3 build:server: `tsc && rm -rf lib/__spec__ lib/**/__spec__`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nucleus-server@1.1.3 build:server script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Me\AppData\Roaming\npm-cache\_logs\2020-04-14T23_17_11_075Z-debug.log
[nodemon] app crashed - waiting for file changes befor46514ms building modules
30ms sealing
2ms optimizing
1ms basic module optimization
8ms module optimization
2ms advanced module optimization
1ms basic chunk optimization
0ms chunk optimization
1ms advanced chunk optimization
1ms module and chunk tree optimization
26ms module reviving
1ms module order optimization
15ms module id optimization
16ms chunk reviving
4ms chunk order optimization
7ms chunk id optimization
34ms hashing
2ms module assets processing
1365ms chunk assets processing
8ms additional chunk assets processing

Start with the build:server command run by yarn dev and the tsconfig.public.json configuration mentioned in the report. Reproduce on Windows, then verify that the server build no longer fails at the rm -rf cleanup step and that yarn dev reaches the application instead of showing Cannot GET /.

Written by the indexing model from the issue text.