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

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.3 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

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
    View changes on GitHub

v2.0.0

Compare Source

Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

🚨 Breaking Changes
🚀 Features

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone Asia/Tokyo, 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 force-pushed the renovate/major-2-vitest-monorepo branch 2 times, most recently from 1e80f3b to 9142e80 Compare July 15, 2024 10:22
@renovate renovate bot force-pushed the renovate/major-2-vitest-monorepo branch 3 times, most recently from 71803fa to 50f49db Compare July 28, 2024 23:09
@renovate renovate bot force-pushed the renovate/major-2-vitest-monorepo branch 2 times, most recently from 66f657e to 57c89bd Compare August 4, 2024 20:17
@renovate renovate bot force-pushed the renovate/major-2-vitest-monorepo branch 3 times, most recently from d80a031 to a969068 Compare September 15, 2024 22:52
@renovate renovate bot force-pushed the renovate/major-2-vitest-monorepo branch from a969068 to 90a5b57 Compare September 22, 2024 21:31
@renovate renovate bot force-pushed the renovate/major-2-vitest-monorepo branch 2 times, most recently from 64b85ac to 4fa083a Compare October 6, 2024 19:17
@renovate renovate bot force-pushed the renovate/major-2-vitest-monorepo branch from 4fa083a to bd50132 Compare October 14, 2024 20:52
@renovate renovate bot force-pushed the renovate/major-2-vitest-monorepo branch from bd50132 to ce8c7f7 Compare October 21, 2024 04:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants