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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency vite-node to v2 #4

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

chore(deps): update dependency vite-node to v2 #4

wants to merge 1 commit into from
+44 −229

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 12, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite-node (source) 0.34.7 -> 2.1.4 age adoption passing confidence

Release Notes

vitest-dev/vitest (vite-node)

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.

Potential Breaking Change
  • workspace:
    • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6316 (afdcb)
    • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
    • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
    • This change doesn't affect non-glob usage.
   🚀 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

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

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

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - "before 4am on Monday" (UTC).

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

♻ Rebasing: Whenever PR is behind base branch, 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-vitest-monorepo branch 3 times, most recently from 7be61a8 to d2ffe7a Compare December 12, 2023 14:08
@netlify Netlify
Copy link

netlify bot commented Dec 12, 2023 •
edited
Loading

❌ Deploy Preview for splendorous-croquembouche-1a931e failed.

Name Link
🔨 Latest commit f7a8dba
🔍 Latest deploy log https://app.netlify.com/sites/splendorous-croquembouche-1a931e/deploys/671f9c57382f3200088d28ea

@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 3092bcb to 5f9ea7c Compare December 25, 2023 00:18
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from 6bbe3cd to 6e5a3ac Compare January 5, 2024 09:35
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 6e7c82b to ab55bdc Compare January 17, 2024 18:43
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 4ec0ac5 to 4114d87 Compare January 26, 2024 18:48
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 4114d87 to 5b75ce0 Compare February 5, 2024 03:01
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 761b6d8 to a031ff9 Compare February 16, 2024 18:12
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from eaba08e to 9d298d8 Compare February 26, 2024 01:36
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 9d298d8 to 5004e98 Compare March 4, 2024 01:27
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from c42aae6 to 1be89b8 Compare March 15, 2024 11:35
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from affdb97 to 06a8926 Compare March 25, 2024 03:20
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 4 times, most recently from 48d3045 to 7bcae2e Compare March 31, 2024 09:55
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 7bcae2e to abb0036 Compare April 11, 2024 20:20
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from 03b1baa to e2a215b Compare April 30, 2024 11:47
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from e2a215b to ff2bcb0 Compare May 3, 2024 15:56
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ff2bcb0 to 8936ffa Compare July 9, 2024 16:08
@renovate renovate bot changed the title chore(deps): update dependency vite-node to v1 chore(deps): update dependency vite-node to v2 Jul 9, 2024
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 745fb84 to c4985ed Compare July 15, 2024 13:58
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from c4985ed to 0b118db Compare July 22, 2024 09:50
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 0b118db to 13d4a0b Compare July 31, 2024 10:48
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from e552032 to ff2fc85 Compare September 13, 2024 16:24
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from ff2fc85 to 2023ab6 Compare September 21, 2024 13:32
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 2023ab6 to 2ff07be Compare October 2, 2024 20:01
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from 2ff07be to b5cce25 Compare October 14, 2024 11:21
@renovate renovate bot force-pushed the renovate/major-vitest-monorepo branch from b5cce25 to f7a8dba Compare October 28, 2024 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants