Resolve high severity vulnerabilities

[theholla]

Issue

Running npm install shows that this package contains 180 high severity vulnerabilities (and some spam). All can be resolved using npm audit fix.

The affected dependencies should be upgraded.

Versions

Node v10.17.0
npm 6.11.3

Logs

$ npm i

> fsevents@1.2.9 install /Users/dianaholland/dev/swagger-parser/node_modules/watchify/node_modules/fsevents
> node install

node-pre-gyp WARN Using request for node-pre-gyp https download 
[fsevents] Success: "/Users/dianaholland/dev/swagger-parser/node_modules/watchify/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" is installed via remote

> fsevents@1.2.9 install /Users/dianaholland/dev/swagger-parser/node_modules/watchpack/node_modules/fsevents
> node install

node-pre-gyp WARN Using request for node-pre-gyp https download 
[fsevents] Success: "/Users/dianaholland/dev/swagger-parser/node_modules/watchpack/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" is installed via remote

> node-sass@4.12.0 install /Users/dianaholland/dev/swagger-parser/node_modules/node-sass
> node scripts/install.js

Cached binary found at /Users/dianaholland/.npm/node-sass/4.12.0/darwin-x64-64_binding.node

> core-js@2.6.9 postinstall /Users/dianaholland/dev/swagger-parser/node_modules/core-js
> node scripts/postinstall || echo "ignore"

...
spam
...

> node-sass@4.12.0 postinstall /Users/dianaholland/dev/swagger-parser/node_modules/node-sass
> node scripts/build.js

Binary found at /Users/dianaholland/dev/swagger-parser/node_modules/node-sass/vendor/darwin-x64-64/binding.node
Testing binary
Binary is fine
added 1457 packages from 1528 contributors and audited 13496 packages in 22.831s
found 180 high severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details

[JamesMessinger]

Fixed by #130