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 dependency vitest to v2 #184

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 14, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) ^1.6.0 -> ^2.1.5 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

v2.1.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.1.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.0

Compare Source

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

  await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()

  const [firstPost] = screen.getByRole('listitem').all()

  await firstPost.getByRole('button', { name: 'Delete' }).click()

  expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.0.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.0.2

Compare Source

v2.0.1

Compare Source

   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - "before 12pm 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.


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

This PR was generated by Mend Renovate. View the repository job log.

@ijsblokjeee ijsblokjeee bot added Dependencies 🚀 PRs and Issues related to dependencies Chore 🧹 labels Jul 14, 2024
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 26b3ef9 to e15737d Compare July 15, 2024 10:24
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from e15737d to 93a67d8 Compare July 22, 2024 11:59
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 93a67d8 to e06dd73 Compare July 31, 2024 12:17
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 240e5f9 to cd68064 Compare September 13, 2024 17:16
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from cd68064 to 6357be6 Compare October 2, 2024 16:55
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 6357be6 to 420d6a6 Compare October 14, 2024 19:10
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 420d6a6 to 4d7d89c Compare October 28, 2024 12:44
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 4d7d89c to 046d3d8 Compare November 13, 2024 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chore 🧹 Dependencies 🚀 PRs and Issues related to dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants