this will be the new baseline for 6.0.0

Fixes N/A

3 -> 4

Fixes N/A

this brings minimatch up to the latest working major
version, the next bump will require some reworking

Fixes N/A

This prevents a warning that occurs when output.filename
is set to '[name].js'. Because this is the default, there
is no need to warn the user as no change will happen.

Fixes #550

this updates minimatch to 9, which no longer has a
default export and must be destructured.

Fixes N/A

this brings all babel dependencies up to the latest
versions

Fixes N/A

Bumps [fsevents](https://github.com/fsevents/fsevents) from 1.2.4 to 1.2.13.
- [Release notes](https://github.com/fsevents/fsevents/releases)
- [Commits](fsevents/fsevents@v1.2.4...v1.2.13)

---
updated-dependencies:
- dependency-name: fsevents
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [json5](https://github.com/json5/json5) from 0.5.1 to 2.2.3.
- [Release notes](https://github.com/json5/json5/releases)
- [Changelog](https://github.com/json5/json5/blob/main/CHANGELOG.md)
- [Commits](json5/json5@v0.5.1...v2.2.3)

---
updated-dependencies:
- dependency-name: json5
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

despite the breaking changes, this all still works fine

Fixes N/A

...

Fixes N/A

this is not used in either the project or tests and has a
strict dependency on webpack 4.

this also bumps the package lock and removes yarn
lock

Fixes N/A

this website for nodesecurity.io is dead as a doornail
I think its time to remove this.

Fixes N/A

these are unused and just cause auditing issues

Fixes N/A

...

Fixes N/A

...

Fixes N/A

* remove gitter, its just full of spam, github issues /
discussion can fill that gap
* remove travis build, doesn't seem to be active now
* remove dependencies badge, its dead

Fixes N/A

Bumps [yargs-parser](https://github.com/yargs/yargs-parser) to 20.2.9 and updates ancestor dependency [@commitlint/cli](https://github.com/conventional-changelog/commitlint/tree/HEAD/@commitlint/cli). These dependencies need to be updated together.


Updates `yargs-parser` from 10.1.0 to 20.2.9
- [Release notes](https://github.com/yargs/yargs-parser/releases)
- [Changelog](https://github.com/yargs/yargs-parser/blob/main/CHANGELOG.md)
- [Commits](yargs/yargs-parser@v10.1.0...yargs-parser-v20.2.9)

Updates `@commitlint/cli` from 7.6.1 to 18.0.0
- [Release notes](https://github.com/conventional-changelog/commitlint/releases)
- [Changelog](https://github.com/conventional-changelog/commitlint/blob/master/@commitlint/cli/CHANGELOG.md)
- [Commits](https://github.com/conventional-changelog/commitlint/commits/v18.0.0/@commitlint/cli)

---
updated-dependencies:
- dependency-name: yargs-parser
  dependency-type: indirect
- dependency-name: "@commitlint/cli"
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

...

Fixes N/A

seemed disrespectful 🤷

Fixes N/A

This reverts commit 701a082.

this will often break the inner workings of karma-webpack
due to a number of issues coming in about this in particular
it has been decided that it is best to ignore these kinds
of customizations and log a warning that they are discarded

Fixes #491

it seems this package is replaced, I'll seek guidance on 
whatever the current release process is and go from
there.

Fixes N/A

this gets us back to 0 known security issues

Fixes N/A

Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.14.8 to 1.15.4.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](follow-redirects/follow-redirects@v1.14.8...v1.15.4)

---
updated-dependencies:
- dependency-name: follow-redirects
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

...

Fixes N/A

Co-authored-by: Cody Mikol <cody.mikol@boltstech.com>

we should not dictate this behavior, just warning
users that this may lead to unexpected behavior
should suffice.

Fixes #587

Co-authored-by: Cody Mikol <cody.mikol@boltstech.com>

Bumps [ip](https://github.com/indutny/node-ip) from 1.1.8 to 1.1.9.
- [Commits](indutny/node-ip@v1.1.8...v1.1.9)

---
updated-dependencies:
- dependency-name: ip
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.5 to 1.15.6.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](follow-redirects/follow-redirects@v1.15.5...v1.15.6)

---
updated-dependencies:
- dependency-name: follow-redirects
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

'settig' -> 'setting'