vercel[bot]
commented
1 year ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| programming-in-th | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Aug 20, 2023 1:04am |
github-actions[bot]
This PR contains the following updates:
5.17.0->6.0.1Release Notes
testing-library/jest-dom (@testing-library/jest-dom)
### [`v6.0.1`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.0.1) [Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.0.0...v6.0.1) ##### Bug Fixes - matchers type is making the global expect unsafe ([#513](https://togithub.com/testing-library/jest-dom/issues/513)) ([bdb34f1](https://togithub.com/testing-library/jest-dom/commit/bdb34f12959578c77b18b0c0910d512768b20ab0)) ### [`v6.0.0`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.0.0) [Compare Source](https://togithub.com/testing-library/jest-dom/compare/v5.17.0...v6.0.0) ##### Features - local types, supporting jest, [@jest/globals](https://togithub.com/jest/globals), vitest ([#511](https://togithub.com/testing-library/jest-dom/issues/511)) ([4b764b9](https://togithub.com/testing-library/jest-dom/commit/4b764b9f6a7b564d7f8ec0e9b0c6ba9cc875f2b8)) ##### BREAKING CHANGES - Removes the extend-expect script. Users should use the default import path or one of the new test platform-specific paths to automatically extend the appropriate "expect" instance. extend-expect was not documented in the Readme, so this change should have minimal impact. Users can now use the following import paths to automatically extend "expect" for their chosen test platform: - [@testing-library/jest-dom](https://togithub.com/testing-library/jest-dom) - jest ([@types/jest](https://togithub.com/types/jest)) - @testing-library/jest-dom/jest-globals - [@jest/globals](https://togithub.com/jest/globals) - @testing-library/jest-dom/vitest - vitest For example: import '@testing-library/jest-dom/jest-globals' Importing from one of the above paths will augment the appropriate matcher interface for the given test platform, assuming the import is done in a .ts file that is included in the user's tsconfig.json. It's also (still) possible to import the matchers directly without side effects: import \* as matchers from '@testing-library/jest-dom/matchers' - Update kcd-scripts - Drop node < 14Configuration
📅 Schedule: Branch creation - "before 4am on sunday" (UTC), 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.