[Snyk] Upgrade ava from 5.3.1 to 6.4.1 #36
Conversation
Snyk has created this PR to upgrade ava from 5.3.1 to 6.4.1. See this package in npm: ava See this project in Snyk: https://app.snyk.io/org/hashim21223445/project/4572145c-469e-45e8-9a07-0c68276f5299?utm_source=github&utm_medium=referral&page=upgrade-pr
|
Review changes with |
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Summary of ChangesHello @hashim21223445, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request, automatically generated by Snyk, updates the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request upgrades ava from version 5.3.1 to 6.4.1, which is a major version jump. While this upgrade addresses several security vulnerabilities, it also introduces significant breaking changes as detailed in the release notes for ava@6.0.0. The most critical change is the new requirement for Node.js version 18.18 or higher. The project's package.json currently specifies support for Node.js >=14, which is now incompatible with the testing framework. This will need to be addressed by updating the engines field, which constitutes a breaking change for consumers of this package.
| "analytics": "^0.2.0", | ||
| "analytics-plugin-ga": "^0.2.0", | ||
| "ava": "^5.3.1", | ||
| "ava": "^6.4.1", |
There was a problem hiding this comment.
Upgrading ava to version 6.x introduces a new minimum Node.js version requirement. According to the ava@6.0.0 release notes, it requires Node.js 18.18, 20.8, or 21.
Your package.json currently declares support for Node.js >=14 in the engines field. This mismatch will cause the tests to fail on older Node.js versions that are supposedly supported.
To resolve this, you must update the engines field in package.json to reflect the new requirement, for example:
"engines": {
"node": ">=18.18"
}Please be aware that this is a breaking change for the consumers of this package who might be using older Node.js versions.
Snyk has created this PR to upgrade ava from 5.3.1 to 6.4.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 10 versions ahead of your current version.
The recommended version was released 5 months ago.
Issues fixed by the recommended upgrade:
SNYK-JS-CROSSSPAWN-8303230
SNYK-JS-SEMVER-3247795
SNYK-JS-SEMVER-3247795
SNYK-JS-SEMVER-3247795
SNYK-JS-INFLIGHT-6095116
SNYK-JS-JSYAML-13961110
SNYK-JS-BRACEEXPANSION-9789073
npm:debug:20170905
Release notes
Package name: ava
-
6.4.1 - 2025-07-12
- Keep test worker alive until explicitly freed by @ matz3 in #3391
- @ matz3 made their first contribution in #3391
-
6.4.0 - 2025-06-07
- AVA is now tested with Node.js 24 (but no longer v23) #3379
- We're now publishing to npm with provenance attestations #3385
- @ mmulet made their first contribution in #3372
- @ kebbell made their first contribution in #3348
-
6.3.0 - 2025-05-02
- Update dependencies, addressing
- Do not count writes to stdout/stderr as non-idling activity for timeouts by @ mdouglass in #3374
- @ mdouglass made their first contribution in #3374
-
6.2.0 - 2024-10-27
- Add
- Add Node.js 23 to supported engines (and test matrix) in #3346
- @ thoughtsunificator made their first contribution in #3345
-
6.1.3 - 2024-05-05
- Include Node.js 22 in supported engines and test matrix by @ lenovouser in #3328
- Add VS Code debugging instructions for Yarn PnP projects by @ bitjson in #3317
- Document
- @ bitjson made their first contribution in #3317
- @ turadg made their first contribution in #3321
- @ lenovouser made their first contribution in #3328
-
6.1.2 - 2024-02-28
- Fix throws assertions rejecting falsy values when
-
6.1.1 - 2024-01-29
- Fix 'previous failures' in watch mode always incrementing by @ novemberborn in #3297
-
6.1.0 - 2024-01-21
-
-
-
-
6.0.1 - 2023-12-06
- Ensure watch mode works outside of its integration tests by @ novemberborn in #3273
-
6.0.0 - 2023-12-04
-
-
-
- Watch mode can no longer be started via the
- The
- Watch mode now uses the built-in
-
-
-
- If such modules export a default function, this function is now invoked.
- Local files are loaded through
- Internal events can now be observed (experimentally). See #3247 by @ codetheweb. It’s experimental and undocumented.
- You can now use
- Code coverage is flushed to disk at opportune moments. #3220
- @ sculpt0r made their first contribution in #3184
- @ ZachHaber made their first contribution in #3233
- @ adiSuper94 made their first contribution in #3245
- @ bricker made their first contribution in #3250
-
5.3.1 - 2023-06-16
from ava GitHub release notesWhat's Changed
New Contributors
Full Changelog: v6.4.0...v6.4.1
What's Changed
Interactive watch mode filters
@ mmulet did fantastic work to spearhead interactive watch mode filters. You can now filter test files by glob patterns, and tests by matching their titles. It's just like you already could from the CLI itself, but now without exiting AVA 🚀 #3372
As part of this work we've removed the "sticky"
.only()behavior #3381Examples
We've been remiss in merging #3335 which updates the examples to use AVA 6. It's done now, examples are up to date and it's all due to @ tommy-mitchell 👏
New Contributors
Full Changelog: v6.3.0...v6.4.0
What's Changed
npm auditwarnings by @ novemberborn in #3377New Contributors
Full Changelog: v6.2.0...v6.3.0
What's Changed
filterNodeArgumentsForWorkerThreadsoption in #3336New Contributors
Full Changelog: v6.1.3...v6.2.0
What's Changed
serialconfiguration option by @ turadg in #3321New Contributors
Full Changelog: v6.1.2...v6.1.3
What's Changed
any: trueby @ gibson042 in #3313Full Changelog: v6.1.1...v6.1.2
What's Changed
Full Changelog: v6.1.0...v6.1.1
What's Changed
Implement
registerCompletionHandler()by @ novemberborn in #3283AVA 6 expects test code to clean up gracefully when the tests are complete, allowing the test environment (worker thread or child process) to exit. If this does not happen, AVA will report a timeout. You can use
registerCompletionHandler()to perform any other clean up (or indeed exit the process) after AVA has completed the test execution. See the description here.Fix potential bug with watch mode when no failed test files are written by @ novemberborn in #3287
Fix
ava/internalESM type module by @ codetheweb in #3292Full Changelog: v6.0.1...v6.1.0
What's Changed
Full Changelog: v6.0.0...v6.0.1
Breaking Changes
AVA now requires Node.js versions 18.18, 20.8 or 21. Versions 14 and 16 are no longer supported. #3251 #3216
When tests finish, worker threads or child processes are no longer exited through
proces.exit(). If your test file does not exit on its own, the test run will time out. #3260Changes to watch mode #3218:
ava.config.*orpackage.jsonconfiguration.ignoredByWatcherconfiguration has moved to thewatchModeobject, under theignoreChangeskey.fs.watch()in recursive mode. This is supported on Linux in Node.js 20 or newer, and MacOS and Windows in Node.js 18 as well. There are caveats to keep in mind.Failed assertions now throw, meaning that any subsequent code is not executed. This also impacts the type definitions. #3246
Only native errors are now considered errors by the
t.throws()andt.throwsAsync()assertions.Object.create(Error.prototype)is not a native error. #3229Changes to modules loaded through the
requireconfiguration #3184:@ ava/typescriptif necessary.Improvements
Rewritten watcher
The watcher has been rewritten. It’s now built on
fs.watch()in recursive mode.@ vercel/nftis used to perform static dependency analysis, supporting ESM and CJS imports for JavaScript & TypeScript source files. This is a huge improvement over the previous runtime tracking of CJS imports, which did not support ESM.Integration with
@ ava/typescripthas been improved. The watcher can now detect a change to a TypeScript source file, then wait for the corresponding build output to change before re-running tests.The ignoredByWatcher configuration has moved to the watchMode object, under the ignoreChanges key.
See #3218 and #3257.
Failed assertions now throw
Assertions now throw a
TestFailureerror when they fail. This error is not exported or documented and should not be used or thrown manually. You cannot catch this error in order to recover from a failure, uset.try()instead.All assertions except for
t.throws()andt.throwsAsync()now returntruewhen they pass. This is useful for some of the assertions in TypeScript where they can be used as a type guard.Committing a failed
t.try()result now also throws.See #3246.
t.throws()andt.throwsAsync()can now expect any errorBy default, the thrown error (or rejection reason) must be a native error. You can change the assertion to expect any kind of error by setting
any: truein the expectation object:See #3245 by @ adiSuper94.
The
requireconfiguration is now more powerfulIt now loads ES modules.
Local files are loaded through
@ ava/typescriptif necessary, so you can also write these in TypeScript.If there is a default export function, it is invoked after loading. The function is awaited so it can do asynchronous setup before further modules are loaded. Arguments from the configuration can be passed to the function (as a [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone)).
See #3184 by @ sculpt0r.
Other changes worth noting
t.timeout.clear()to restore a previoust.timeout(). #3221New Contributors
Full Changelog: v5.3.1...v6.0.0
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: