Skip to content

chore(tests): audit karma test suite packages#3178

Merged
rwaskiewicz merged 8 commits intomainfrom
2021.12.09-sec
Jan 4, 2022
Merged

chore(tests): audit karma test suite packages#3178
rwaskiewicz merged 8 commits intomainfrom
2021.12.09-sec

Conversation

@rwaskiewicz
Copy link
Copy Markdown
Member

@rwaskiewicz rwaskiewicz commented Dec 9, 2021

Pull request checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Build (npm run build) was run locally and any changes were pushed
  • Unit tests (npm test) were run locally and passed
  • E2E Tests (npm run test.karma.prod) were run locally and passed
  • Prettier (npm run prettier) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

What is the current behavior?

There are several vulnerabilities being reported via GitHub about packages in our Karma tests.
GitHub Issue Number: N/A

What is the new behavior?

  • commit 1 - results of running npm audit fix --only=dev within the test/karma
    directory. a good deal of the security vulnerabilities that GitHub warns
    us about are in this directory, and many can be fixed (assuming packages
    follow semver) with a quick audit+fix
  • commit 2 - upgrade webpack-cli to v4 from v3 to resolve security issuse found in
    v3. there appears to be only one breaking change in v4 insofar as i can
    tell (--plugin is removed) and it does not affect us since we use this
    cli in such a limited capacity
  • commit 6 - install karma-jasmine v4. the only breaking change is v4 drops node 8
    support and adds node 14 support, which does not apply to this section
    of the codebase
  • remaining commits - remove unused packages

Does this introduce a breaking change?

  • Yes
  • No

Testing

between each commit, npm ci && npm run karma.prod was run from the tests/karma directory

Other information

I did not attempt to upgrade Karma in the scope of this PR, which is reporting a few vulnerabilities ATM

results of running `npm audit fix --only=dev` within the `test/karma`
directory. a good deal of the security vulnerabilities that GitHub warns
us about are in this directory, and many can be fixed (assuming packages
follow semver) with a quick audit+fix
upgrade webpack-cli to v4 from v3 to resolve security issuse found in
v3. there appears to be only one breaking change in v4 insofar as i can
tell (`--plugin` is removed) and it does not affect us since we use this
cli in such a limited capacity
install karma-jasmine v4. the only breaking change is v4 drops node 8
support and adds node 14 support, which does not apply to this section
of the codebase
@rwaskiewicz rwaskiewicz marked this pull request as ready for review December 9, 2021 15:43
@rwaskiewicz rwaskiewicz requested a review from a team December 9, 2021 15:43
@rwaskiewicz rwaskiewicz merged commit c7f75f6 into main Jan 4, 2022
@rwaskiewicz rwaskiewicz deleted the 2021.12.09-sec branch January 4, 2022 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants