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 #101

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 8, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) ^1.5.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 - 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.

🔕 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.

@renovate renovate bot requested a review from Hebilicious as a code owner July 8, 2024 13:30
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from cdc50d2 to 947c556 Compare July 15, 2024 10:39
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 947c556 to 01e7d87 Compare July 22, 2024 12:01
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 01e7d87 to e3d1b49 Compare July 31, 2024 14:24
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from ef57611 to 7311c9f Compare September 13, 2024 16:38
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7311c9f to fa832bd Compare October 2, 2024 16:27
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from fa832bd to 61a54c1 Compare October 14, 2024 20:39
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 61a54c1 to c7b2d5c Compare October 28, 2024 13:39
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from c7b2d5c to 36937e3 Compare November 13, 2024 16:24
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.

0 participants