Fix vulnerabilities

[tjinauyeung]

Two vulnerabilities were found in the project.

• One in gulp-delete-lines package, which was not used, so removed it from devDependencies.
• One is deeply nested and depended on by many packages. We can use the npm overrides field to manually set this one to a specific version

Context

The surface area of the override is limited to the build scripts which lowers the risk on the output.

We can test everything still works by:

1. Running the build scripts and monitor for thrown errors,
2. Running the demos after building

npm audit report

glob-parent  <5.1.2
Severity: high
glob-parent before 5.1.2 vulnerable to Regular Expression Denial of Service in enclosure regex - https://github.com/advisories/GHSA-ww39-953v-wcq6
fix available via `npm audit fix --force`
Will install [email protected], which is a breaking change
node_modules/chokidar/node_modules/glob-parent
node_modules/glob-stream/node_modules/glob-parent
  chokidar  1.0.0-rc1 - 2.1.8
  Depends on vulnerable versions of glob-parent
  node_modules/chokidar
    glob-watcher  >=3.0.0
    Depends on vulnerable versions of chokidar
    node_modules/glob-watcher
  glob-stream  5.3.0 - 6.1.0
  Depends on vulnerable versions of glob-parent
  node_modules/glob-stream
    vinyl-fs  >=2.4.2
    Depends on vulnerable versions of glob-stream
    node_modules/vinyl-fs
      gulp  >=4.0.0
      Depends on vulnerable versions of glob-watcher
      Depends on vulnerable versions of vinyl-fs
      node_modules/gulp

lodash.template  <4.5.0
Severity: critical
Prototype Pollution in lodash - https://github.com/advisories/GHSA-jf85-cpcp-j695
No fix available
node_modules/gulp-util/node_modules/lodash.template
  gulp-util  >=1.1.0
  Depends on vulnerable versions of lodash.template
  node_modules/gulp-util
    gulp-delete-lines  *
    Depends on vulnerable versions of gulp-util
    node_modules/gulp-delete-lines

9 vulnerabilities (6 high, 3 critical)

[sam-pitch]

how can we test that the override doesn't cause any problems before merging? Just try exporting in our app locally with this branch?

[tjinauyeung]

The surface area of the override is limited to the build scripts which lowers the risk on the output.

We can test everything still works by:

1. Running the build scripts and monitor for thrown errors,
2. Running the demos after building

[pastafari]

A functional test would be to add a tag on this branch, import it into pitch-app, and see if export continues to work

[pastafari]

Changes look small enough and contained to gulp, shall we try this out?