Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: resolve npm audit issues #3378

Merged
merged 11 commits into from
Feb 11, 2022
Merged

chore: resolve npm audit issues #3378

merged 11 commits into from
Feb 11, 2022

Conversation

WilcoFiers
Copy link
Contributor

Resolve issues reported by npm audit. This required replacing karma-mocha-reporter with karma-spec-reporter. Since karma-mocha-report hasn't been published for 4 years I thought it'd best to just replace it. We'll have a slightly different test report as a result, but it's minor.

Also bumping node version to >=12. There is no way axe-core tests can run on Node v4. Mocha v9 only runs on Node v12+.

@WilcoFiers WilcoFiers requested a review from a team as a code owner February 4, 2022 12:06
@WilcoFiers WilcoFiers force-pushed the update-dependencies branch 2 times, most recently from d7fd5df to 214c318 Compare February 4, 2022 16:01
@WilcoFiers WilcoFiers merged commit 27ad236 into develop Feb 11, 2022
@WilcoFiers WilcoFiers deleted the update-dependencies branch February 11, 2022 18:46
straker pushed a commit that referenced this pull request May 12, 2022
* chore: resolve npm audit issues

* fix ACT karma config

* chore(runPartial): skip tests in IE

* ci: try upgrading win executor

* Update config.yml

* Update config.yml

* More tests not running in IE

* More of these

* bump karma version

* avoid using .finally()
@@ -4,7 +4,7 @@
"version": "4.4.1",
"license": "MPL-2.0",
"engines": {
"node": ">=4"
"node": ">=12"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: this is a breaking change and requires a semver-major update. See #3537.

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.

3 participants