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(deps): update all non-major dependencies #21

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 5, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@testing-library/jest-dom ^5.16.4 -> ^5.16.5 age adoption passing confidence
@testing-library/react ^12.1.2 -> ^12.1.5 age adoption passing confidence
@testing-library/user-event ^14.4.1 -> ^14.4.3 age adoption passing confidence
@tsconfig/vite-react ^1.0.0 -> ^1.0.1 age adoption passing confidence
@types/react (source) ^17.0.38 -> ^17.0.60 age adoption passing confidence
@types/react-dom (source) ^18.0.6 -> ^18.2.4 age adoption passing confidence
c8 ^7.11.3 -> ^7.14.0 age adoption passing confidence
jsdom ^20.0.0 -> ^20.0.3 age adoption passing confidence
vitest ^0.14.1 -> ^0.32.0 age adoption passing confidence

Release Notes

testing-library/jest-dom

v5.16.5

Compare Source

Bug Fixes
testing-library/react-testing-library

v12.1.5

Compare Source

Bug Fixes

v12.1.4

Compare Source

Bug Fixes
  • Match runtime type of baseElement in TypeScript types (#​1023) (96ed8da)

v12.1.3

Compare Source

Bug Fixes
testing-library/user-event

v14.4.3

Compare Source

Bug Fixes

v14.4.2

Compare Source

Bug Fixes
bcoe/c8

v7.14.0

Compare Source

Features
  • added a new CLI arg --merge-async to asynchronously and incrementally merge process coverage files to avoid OOM due to heap exhaustion (#​469) (45f2f84)

v7.13.0

Compare Source

Features

v7.12.0

Compare Source

Features
7.11.3 (2022-05-16)
Bug Fixes
7.11.2 (2022-04-20)
Bug Fixes
  • perf: cache this.exclude.shouldInstrument for improved performance (#​388) (8b36f23)
7.11.1 (2022-04-20)
Bug Fixes
jsdom/jsdom

v20.0.3

Compare Source

  • Updated dependencies, notably w3c-xmlserializer, which fixes using DOMParser on XML documents containing emoji.

v20.0.2

Compare Source

  • Fixed xhr.abort() to no longer give an exception when the constructed XMLHttpRequest was invalid. (whamtet)
  • Fixed event.getModifierState() on MouseEvent and KeyboardEvent instances to properly consult the ctrlKey, altKey, metaKey, and shiftKey properties of the event. (juzerzarif)
  • Fixed custom element creation to not be affected by any modifications to the window.customElements property. (bicknellr)

v20.0.1

Compare Source

  • Improved the performance of appending <option> elements to <select> elements. (TheHound)
  • Fixed location.pathname getter to not crash when the JSDOM instance was created using an opaque-path URL, including the default URL of about:blank.
  • Fixed crypto.getRandomValues() to accept typed array subclasses. (sebamarynissen)
  • Updated various dependency minor versions. Notably, nwsapi fixed some selectors bugs, and tough-cookie fixed some cookie bugs.
vitest-dev/vitest

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

v0.30.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.30.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.29.8

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.29.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.4

Compare Source

   🚀 Features
  • --test-timeout CLI argument  -  by @​AriPerkkio in [https://github.com/vitest-dev/vitest/issue

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.

@renovate renovate bot changed the title chore(deps): update dependency @testing-library/jest-dom to ^5.16.4 chore(deps): update all non-major dependencies Apr 7, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from ba04553 to 5aa081d Compare April 12, 2022 18:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5aa081d to 4249f52 Compare April 25, 2022 18:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 218be91 to 85e063c Compare May 12, 2022 19:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 85e063c to 004a325 Compare May 18, 2022 18:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 067bae5 to 94acfe7 Compare June 10, 2022 14:21
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from d53bf4d to 0ce352a Compare June 21, 2022 12:10
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0ce352a to c8f5c09 Compare June 24, 2022 15:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 2d82cd3 to 189e382 Compare July 9, 2022 10:18
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from a9a52a3 to b5c2264 Compare July 19, 2022 18:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from ee60e26 to 5e16270 Compare July 31, 2022 09:44
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 2d20253 to 9830ac8 Compare August 3, 2022 04:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9830ac8 to 8cbc40e Compare August 4, 2022 23:03
@renovate
Copy link
Contributor Author

renovate bot commented Aug 4, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm notice 
npm notice New major version of npm available! 8.19.4 -> 9.6.7
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.7>
npm notice Run `npm install -g npm@9.6.7` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: react-app@0.1.0
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"<18.0.0" from @testing-library/react@12.1.5
npm ERR! node_modules/@testing-library/react
npm ERR!   dev @testing-library/react@"^12.1.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/c737f6/3a61d0/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/c737f6/3a61d0/cache/others/npm/_logs/2023-06-06T19_32_43_886Z-debug-0.log

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from eab7d7e to 388d39c Compare August 9, 2022 16:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 388d39c to 1ac6476 Compare August 23, 2022 14:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 96dbeda to 9e13f9d Compare September 5, 2022 11:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from dea7b6f to d75e14b Compare September 13, 2022 20:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b54d9a8 to eae5f31 Compare October 2, 2022 08:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from b2f59e6 to c0fae69 Compare March 20, 2023 20:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from ec6e35c to 7c76c28 Compare March 29, 2023 21:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7c76c28 to 0a29859 Compare April 17, 2023 13:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 1828795 to 4a1b0bc Compare June 1, 2023 11:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4a1b0bc to aeac63f Compare June 6, 2023 19:32
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.

None yet

0 participants