npm start not working after npm install

Description

Throws error

Expected Behavior

README says npm start works

Actual Behavior

patrikx3@workstation:~/Projects/videogular2$ npm start

> videogular2@0.0.0-semantically-released start /home/patrikx3/Projects/videogular2
> run-p "watch:ts" "start:coverage-server"

> videogular2@0.0.0-semantically-released watch:ts /home/patrikx3/Projects/videogular2
> watch "npm run build" src

> videogular2@0.0.0-semantically-released start:coverage-server /home/patrikx3/Projects/videogular2
> http-server -c-1 -o -p 9875 ./coverage

> Watching src
Starting up http-server, serving ./coverage
Available on:
  http://127.0.0.1:9875
  http://192.168.78.30:9875
  http://192.168.78.31:9875
Hit CTRL-C to stop the server
open: http://127.0.0.1:9875

> videogular2@0.0.0-semantically-released prebuild /home/patrikx3/Projects/videogular2
> npm run clean

> videogular2@0.0.0-semantically-released clean /home/patrikx3/Projects/videogular2
> rimraf -rf ./src/**/*.js && rimraf -rf ./src/**/*.d.ts && rimraf -rf ./compiled

[2020-05-24T10:17:02.757Z]  "GET /" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36"
(node:10828) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
[2020-05-24T10:17:02.768Z]  "GET /" Error (404): "Not found"

> videogular2@0.0.0-semantically-released build /home/patrikx3/Projects/videogular2
> ngc

> videogular2@0.0.0-semantically-released postbuild /home/patrikx3/Projects/videogular2
> npm test

> videogular2@0.0.0-semantically-released test /home/patrikx3/Projects/videogular2
> karma start karma.conf.js

24 05 2020 12:17:08.148:INFO [karma-server]: Karma v5.0.5 server started at http://0.0.0.0:9876/
24 05 2020 12:17:08.149:INFO [launcher]: Launching browsers FirefoxHeadless with concurrency unlimited
24 05 2020 12:17:08.150:ERROR [launcher]: Cannot load browser "FirefoxHeadless"!
  Error: EMFILE: too many open files, open '/home/patrikx3/Projects/videogular2/node_modules/karma/lib/temp_dir.js'
    at Object.openSync (fs.js:458:3)
    at Object.readFileSync (fs.js:360:35)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1152:22)
    at Module.load (internal/modules/cjs/loader.js:977:32)
    at Function.Module._load (internal/modules/cjs/loader.js:877:14)
    at Module.require (internal/modules/cjs/loader.js:1019:19)
    at require (internal/modules/cjs/helpers.js:77:18)
    at /home/patrikx3/Projects/videogular2/node_modules/karma/lib/launchers/process.js:176:56
    at /home/patrikx3/Projects/videogular2/node_modules/karma/lib/launcher.js:24:5
    at Object.FirefoxBrowser (/home/patrikx3/Projects/videogular2/node_modules/karma-firefox-launcher/index.js:175:3)
24 05 2020 12:17:08.151:ERROR [karma-server]: Error: Found 1 load error
    at Server.<anonymous> (/home/patrikx3/Projects/videogular2/node_modules/karma/lib/server.js:189:27)
    at Object.onceWrapper (events.js:416:28)
    at Server.emit (events.js:322:22)
    at emitListeningNT (net.js:1347:10)
    at processTicksAndRejections (internal/process/task_queues.js:83:21)
npm ERR! Test failed.  See above for more details.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! videogular2@0.0.0-semantically-released postbuild: `npm test`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the videogular2@0.0.0-semantically-released postbuild 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!     /home/patrikx3/.npm/_logs/2020-05-24T10_17_08_188Z-debug.log

Steps to Reproduce

npm install
npm start

videogular / videogular2

npm start not working after npm install #900

Description

Expected Behavior

Actual Behavior

Steps to Reproduce