Skip to content
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.

chore(deps): update test packages #157

Closed
wants to merge 4 commits into from
Closed

chore(deps): update test packages #157

wants to merge 4 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 5, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@vitest/coverage-c8 (source) 0.30.1 -> 0.32.2 age adoption passing confidence devDependencies minor
@vitest/ui (source) ^0.30.0 -> ^0.32.0 age adoption passing confidence dependencies minor
happy-dom 9.10.9 -> 9.20.3 age adoption passing confidence dependencies minor
vitest 0.30.1 -> 0.32.2 age adoption passing confidence devDependencies minor
vitest ^0.24.5 || ^0.26.0 || ^0.27.0 || ^0.28.0 || ^0.29.0 || ^0.30.0 -> ^0.24.5 || ^0.26.0 || ^0.27.0 || ^0.28.0 || ^0.29.0 || ^0.30.0 || ^0.32.0 age adoption passing confidence peerDependencies minor
vitest ^0.30.0 -> 0.30.1 age adoption passing confidence devDependencies pin

Release Notes

vitest-dev/vitest

v0.32.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.0

Compare Source

   🚨 Breaking Changes
  • Throw an error, if the module cannot be resolved  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3307 (1ad63)
    • Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction.
  • Improve globs  -  by @​nickmccurdy in https://github.com/vitest-dev/vitest/issues/3392 (19ecc)
    • Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers test.js to be a test file. Also any file in __tests__ is now considered to be a test, not just files with test or spec suffix.
  • Add @vitest/coverage-v8 package  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3339 (82112)
    • Vitest now uses v8 code coverage directly for better performance. @vitest/coverage-c8 is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has c8 as their coverage provider. Please, install the new @vitest/coverage-v8 package if you previously used @vitest/coverage-c8.
  • mocker: Don't restore mock to the original if the module is automocked  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3518 (c1004)
    • spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.0

Compare Source

   🚨 Breaking Changes

  • Remove browser from allowed pools inside poolMatchGlob config option. Please, use Vitest workspaces for running tests in the browser.

  • Move assertion declarations to expect package  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3294 (cf3af)

    • The change should be minor:
    - declare namespace Vi {
+ declare module 'vitest' {
   interface Assertion<T = any> extends CustomMatchers<T> {}
   interface AsymmetricMatchersContaining extends CustomMatchers {}
}
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
capricorn86/happy-dom

v9.20.3

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue where all properties didn't get copied from HTMLUnknownElement to a custom element that is replacing it when it is defined. (#​668)

v9.20.2

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue where CSS variable values where not returned by Window.getComputedStyle() when calling CSSStyleDeclaration.getPropertyValue(). (#​932)

v9.20.1

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem with querySelectorAll() where it didn't always return elements in document order. (#​928)

v9.20.0

Compare Source

🎨 Features
  • Adds support for disabling the simulation of rendering when calculating computed style. The rendering process converts units such as rem, em and cm to pixels, but it is very limited. (#​929)
  • Changes the behavior of converting percentage values to "0px" when calculating computed style (as it fails to convert) to just leave the values.

v9.19.2

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue where attribute selectors with an operator and with a value without quatation marks no longer worked (e.g. "[attr^=value]"). (#​923)

v9.19.1

Compare Source

👷‍♂️ Patch fixes
  • Adds support for the mime type "apng" to XMLHttpRequest

Thank you @​btea for your contribution!

v9.19.0

Compare Source

🎨 Features
  • Adds support for "rem", "em", "vw", "vh", "vmin", "vmax", "cm", "mm", "in", "pt", "pc", "Q" measurement values to Window.getComputedStyle() and Window.matchMedia() (#​921)
  • Adds support for "%" measurement values to Window.getComputedStyle() and Window.matchMedia() when setting font size (other properties will be set to "0px") (#​921)
  • Sets "font: 16px "Times new Roman"" as default font on the <html> when using Window.getComputedStyle() (#​921)
  • Adds support for "outline", "outline-color", "outline-style", "outline-width", "outline-offset", "letter-spacing", "word-spacing" and "text-indent" to CSSStyleDeclaration. (#​921)
  • Adds support for the media query rules "orientation", "prefers-color-scheme", "any-hover", "hover", "any-pointer", "pointer", "display-mode", "width", "height", "min-aspect-ratio", "max-aspect-ratio" and "aspect-ratio" (#​921)
  • Improves support for the media query rules "min-width", "max-width", "min-height" and "max-height" (#​921)
  • Adds support for media types "all", "screen" and "print" to media queries (#​921)
  • Adds support for the "only", "not", "and" and "or" operators to media queries (#​921)
  • Adds support for ranges to media queries (#​921)
  • Adds support for "@​-webkit-keyframes", "@​-webkit-container" and "@​-webkit-supports" to CSS parser (#​921)
👷‍♂️ Patch fixes
  • Adds support for ignoring unknown "@​" rules to the CSS parser. (#​921)
  • Adds support for the "height" property to CSSStyleDeclaration. Not having support for "height" was missed somehow, as we have support for "width". (#​922)

v9.18.3

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue where non-string values did not get converted to strings in CharacterData.data, CharacterData.nodeValue or CharacterData.textContent. (#​819)

v9.18.2

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue in the XML parser where it failed to parse comments including dash characters (-). (#​916)

Thank you @​gtm-nayan for your contribution!

v9.18.1

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue where attribute query selectors using "~" or "|" as operators for finding attributes containing a word did not match when there was only one word. (#​914)

v9.18.0

Compare Source

🎨 Features
  • Adds support for triggering an error event when attempting to fetch a CSS file or Javascript file when it has been disabled using "window.happyDOM.settings.*". (#​849)

v9.17.0

Compare Source

🎨 Features
  • Adds support for "i" and "s" modifiers to attribute query selectors. (#​911)

v9.16.0

Compare Source

🎨 Features
  • Adds support for encoding HTML entities to the XML parser. (#​908)
  • Adds support for escaping text to XMLSerializer.serializeToString(). (#​908)

v9.15.0

Compare Source

🎨 Features

Thank you @​crypto-scythe for your contribution!

v9.14.0

Compare Source

🎨 Features
  • Adds support for Document.links. (#​896)

Thank you @​btea for your contribution!

v9.13.1

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue related to "@​" CSS rules in (e.g. "@​-webkit-keyframes") causing an exception to be thrown in CSSStyleDeclaration. (#​889)

Thank you @​btea for your contribution!

v9.13.0

Compare Source

🎨 Features
  • Improves performance of Element.querySelectorAll(). The performance was decreased after the implementation of document sorting order, due to the fact that it relied on Object.assign() for each match, which is slower than iterating through all matches in the end. (#​909)

v9.12.0

Compare Source

🎨 Features
  • Adds support for the "of selector" to ":nth-child" and ":nth-last-child" query selectors. (#​905)
👷‍♂️ Patch fixes
  • Fixes bug but where "nth-*" query selectors didn't return the correct elements when prefixing "n" with "-". (#​905)

v9.11.0

Compare Source

🎨 Features
  • Refactors the XML parser, which fixes several issues related to parsing complex HTML (e.g. attributes containing ">"). (#​578)
  • Improves performance of XML parsing significantly. (#​578)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@socket-security
Copy link

socket-security bot commented May 5, 2023 •
edited

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

@renovate renovate bot force-pushed the renovate/test-packages branch from 2794e82 to 92fa808 Compare May 5, 2023 12:14
@danielroe
Copy link
Owner

danielroe commented May 5, 2023 •
edited

@antfu Do you have any idea about the failing test here? It looks like the mocking isn't succeeding because the path differs between vi.mock and import...

@antfu
Copy link
Collaborator

antfu commented May 5, 2023

Maybe @sheremet-va has some idea?

@sheremet-va
Copy link

@antfu Do you have any idea about the failing test here? It looks like the mocking isn't succeeding because the path differs between vi.mock and import...

The path cannot differ, but the call order can. Vitest now implements mocking as a plugin that hoists vi.mock and transforms import from into await import. It's possible that your plugin runs after that. Should we ensure that mocking plugin is the last one somehow? @antfu 🤔

@antfu
Copy link
Collaborator

antfu commented May 5, 2023

Yeah, I think we should

@renovate renovate bot force-pushed the renovate/test-packages branch 5 times, most recently from 26059e9 to 4dd035a Compare May 11, 2023 15:32
@renovate renovate bot force-pushed the renovate/test-packages branch 2 times, most recently from c124df2 to 428252e Compare May 15, 2023 10:40
@danielroe
Copy link
Owner

linking vitest-dev/vitest#3308 here

@renovate renovate bot force-pushed the renovate/test-packages branch 3 times, most recently from 0d211ae to ca0cafb Compare May 17, 2023 12:51
@renovate renovate bot changed the title chore(deps): update test packages to v0.31.0 chore(deps): update test packages to v0.31.1 May 17, 2023
@renovate renovate bot force-pushed the renovate/test-packages branch 3 times, most recently from 4423f29 to 523ffe1 Compare May 21, 2023 16:10
@renovate renovate bot changed the title chore(deps): update test packages to v0.31.1 chore(deps): update test packages May 21, 2023
@renovate renovate bot force-pushed the renovate/test-packages branch 4 times, most recently from 38d3062 to 84cccf0 Compare May 28, 2023 03:59
@renovate renovate bot force-pushed the renovate/test-packages branch 2 times, most recently from 6440fc1 to bcf755a Compare May 28, 2023 23:39
@renovate renovate bot force-pushed the renovate/test-packages branch 5 times, most recently from 1ca453d to 7d3a1b4 Compare June 6, 2023 00:27
@socket-security
Copy link

socket-security bot commented Jun 6, 2023 •
edited

New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives1 Size Publisher
@vitest/coverage-v8 🆕 0.32.2 None +3 173 kB oreanno
@vitest/ui ⬆️ 0.30.0...0.32.2 None +0/-14 808 kB oreanno

🚮 Removed packages: @vitest/coverage-c8@0.30.1, h3@1.6.6, vitest@0.30.1

Footnotes

  1. https://docs.socket.dev ↩

@renovate renovate bot force-pushed the renovate/test-packages branch 5 times, most recently from b5147a1 to f02bd02 Compare June 12, 2023 18:01
@danielroe danielroe mentioned this pull request Jun 13, 2023
Closed
@renovate renovate bot force-pushed the renovate/test-packages branch 8 times, most recently from baa22f7 to f57b3ba Compare June 21, 2023 11:20
@renovate
Copy link
Contributor Author

renovate bot commented Jun 21, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

@danielroe danielroe mentioned this pull request Jun 21, 2023
Closed
@antfu antfu mentioned this pull request Jul 17, 2023
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
chore dependencies nuxt-vitest
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@danielroe @antfu @sheremet-va