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

[Snyk] Upgrade ava from 3.15.0 to 6.1.3 #5

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

YoutacRandS-VA
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade ava from 3.15.0 to 6.1.3.

ℹ️ 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.


⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 24 versions ahead of your current version.

  • The recommended version was released on a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Open Redirect
SNYK-JS-GOT-2932019
484 No Known Exploit
Release notes
Package name: ava
  • 6.1.3 - 2024-05-05

    What's Changed

    New Contributors

    Full Changelog: v6.1.2...v6.1.3

  • 6.1.2 - 2024-02-28

    What's Changed

    • Fix throws assertions rejecting falsy values when any: true by @ gibson042 in #3313

    Full Changelog: v6.1.1...v6.1.2

  • 6.1.1 - 2024-01-29

    What's Changed

    Full Changelog: v6.1.0...v6.1.1

  • 6.1.0 - 2024-01-21

    What's Changed

    • Implement registerCompletionHandler() by @ novemberborn in #3283

      AVA 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/internal ESM type module by @ codetheweb in #3292

    Full Changelog: v6.0.1...v6.1.0

  • 6.0.1 - 2023-12-06

    What's Changed

    Full Changelog: v6.0.0...v6.0.1

  • 6.0.0 - 2023-12-04

    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. #3260

    • Changes to watch mode #3218:

      • Watch mode can no longer be started via the ava.config.* or package.json configuration.
      • The ignoredByWatcher configuration has moved to the watchMode object, under the ignoreChanges key.
      • Watch mode now uses the built-in 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() and t.throwsAsync() assertions. Object.create(Error.prototype) is not a native error. #3229

    • Changes to modules loaded through the require configuration #3184:

      • If such modules export a default function, this function is now invoked.
      • Local files are loaded through @ ava/typescript if necessary.

    Improvements

    Rewritten watcher

    The watcher has been rewritten. It’s now built on fs.watch() in recursive mode.

    @ vercel/nft is 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/typescript has 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 TestFailure error 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, use t.try() instead.

    All assertions except for t.throws() and t.throwsAsync() now return true when 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() and t.throwsAsync() can now expect any error

    By 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: true in the expectation object:

    t.throws(() => { throw 'error' }, {any: true})

    See #3245 by @ adiSuper94.

    The require configuration is now more powerful

    It now loads ES modules.

    Local files are loaded through @ ava/typescript if 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

    • Internal events can now be observed (experimentally). See #3247 by @ codetheweb. It’s experimental and undocumented.
    • You can now use t.timeout.clear() to restore a previous t.timeout(). #3221
    • Code coverage is flushed to disk at opportune moments. #3220

    New Contributors

    Full Changelog: v5.3.1...v6.0.0

  • 5.3.1 - 2023-06-16

    What's Changed

    Full Changelog: v5.3.0...v5.3.1

  • 5.3.0 - 2023-05-25

    What's Changed

    New Contributors

    Full Changelog: v5.2.0...v5.3.0

  • 5.2.0 - 2023-02-06

    What's Changed

    New Contributors

    Full Changelog: v5.1.1...v5.2.0

  • 5.1.1 - 2023-01-15

    What's Changed

    Full Changelog: v5.1.0...v5.1.1

  • 5.1.0 - 2022-11-14
  • 5.0.1 - 2022-09-25
  • 5.0.0 - 2022-09-04
  • 4.3.3 - 2022-08-25
  • 4.3.2 - 2022-08-25
  • 4.3.1 - 2022-07-10
  • 4.3.0 - 2022-06-02
  • 4.2.0 - 2022-04-10
  • 4.1.0 - 2022-03-06
  • 4.0.1 - 2022-01-08
  • 4.0.0 - 2022-01-03
  • 4.0.0-rc.1 - 2021-11-01
  • 4.0.0-alpha.2 - 2021-04-06
  • 4.0.0-alpha.1 - 2021-03-21
  • 3.15.0 - 2021-01-01
from ava GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

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:

Snyk has created this PR to upgrade ava from 3.15.0 to 6.1.3.

See this package in npm:
ava

See this project in Snyk:
https://app.snyk.io/org/youtacrands-va/project/4199cd63-b361-4f40-a9fc-dc8ec47d4247?utm_source=github&utm_medium=referral&page=upgrade-pr
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