> fsevents@1.2.9 install /Users/cnorbjerg/Documents/Projects/wfrpg/wfrpg/node_modules/fsevents
> node install

node-pre-gyp WARN Using request for node-pre-gyp https download
[fsevents] Success: "/Users/cnorbjerg/Documents/Projects/wfrpg/wfrpg/node_modules/fsevents/lib/binding/Release/node-v67-darwin-x64/fse.node" is installed via remote

> node-sass@4.11.0 install /Users/cnorbjerg/Documents/Projects/wfrpg/wfrpg/node_modules/node-sass
> node scripts/install.js

Cached binary found at /Users/cnorbjerg/.npm/node-sass/4.11.0/darwin-x64-67_binding.node

> @google-cloud/functions-emulator@1.0.0-beta.6 postinstall /Users/cnorbjerg/Documents/Projects/wfrpg/wfrpg/node_modules/@google-cloud/functions-emulator
> node scripts/upgrade-warning


If you're using the Emulator via the Firebase CLI, you can
disregard this message.

If you're upgrading @google-cloud/functions-emulator, these
are the recommended upgrade steps:

1.  Stop the currently running emulator, if any:

        functions stop

2.  Uninstall the current emulator, if any:

        npm uninstall -g @google-cloud/functions-emulator

3.  Install the new version of the emulator:

        npm install -g @google-cloud/functions-emulator

If you have trouble after upgrading, try deleting the config
directory found in:

    ~/.config/configstore/@google-cloud/functions-emulator

Then restart the emulator. You can also check for any renegade
Node.js emulator processes that may need to be killed:

    ps aux | grep node


> node-sass@4.11.0 postinstall /Users/cnorbjerg/Documents/Projects/wfrpg/wfrpg/node_modules/node-sass
> node scripts/build.js

Binary found at /Users/cnorbjerg/Documents/Projects/wfrpg/wfrpg/node_modules/node-sass/vendor/darwin-x64-67/binding.node
Testing binary
Binary is fine
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN @angular/platform-browser-dynamic@7.0.4 requires a peer of @angular/compiler@7.0.4 but none is installed. You must install peer dependencies yourself.

added 1455 packages from 1150 contributors and audited 42953 packages in 51.297s
found 4 vulnerabilities (1 low, 2 moderate, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details