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

build(deps-dev): Bump the vite group across 1 directory with 6 updates #3037

Closed
wants to merge 1 commit into from
Closed

build(deps-dev): Bump the vite group across 1 directory with 6 updates #3037

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 30, 2024 •
edited
Loading

Bumps the vite group with 6 updates in the / directory:

Package From To
@vitejs/plugin-react 4.3.1 4.3.2
@vitest/coverage-istanbul 2.0.5 2.1.1
vite 5.4.2 5.4.8
vite-plugin-checker 0.7.2 0.8.0
vite-plugin-dts 4.1.0 4.2.3
vitest 2.0.5 2.1.1

Updates @vitejs/plugin-react from 4.3.1 to 4.3.2

Release notes

Sourced from @​vitejs/plugin-react's releases.

v4.3.2

Ignore directive sourcemap error #369

Changelog

Sourced from @​vitejs/plugin-react's changelog.

4.3.2 (2024-09-29)

Ignore directive sourcemap error #369

Commits

Updates @vitest/coverage-istanbul from 2.0.5 to 2.1.1

Release notes

Sourced from @​vitest/coverage-istanbul's releases.

v2.1.1

   🐞 Bug Fixes

    View changes on GitHub

v2.1.0

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 vitest-dev/vitest#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

... (truncated)

Commits
  • 699055e chore: release v2.1.1
  • 9f1fd18 chore: release v2.1.0
  • b2be23e chore: release v2.1.0-beta.7
  • 8ac7011 chore: release v2.1.0-beta.6
  • da52d23 fix(coverage): use project specific vitenode for uncovered files (#6044)
  • 5932a7f feat(coverage): add --exclude-after-remap (#6309)
  • 34199bd feat(browser): support v8 coverage (#6273)
  • 72056b5 chore: release v2.1.0-beta.5
  • e662c7b fix(coverage): warn if vitest and @vitest/* versions don't match (#6317)
  • 67b086b chore: release v2.1.0-beta.4
  • Additional commits viewable in compare view

Updates vite from 5.4.2 to 5.4.8

Changelog

Sourced from vite's changelog.

5.4.8 (2024-09-25)

5.4.7 (2024-09-20)

5.4.6 (2024-09-16)

5.4.5 (2024-09-13)

5.4.4 (2024-09-11)

5.4.3 (2024-09-03)

Commits

Updates vite-plugin-checker from 0.7.2 to 0.8.0

Release notes

Sourced from vite-plugin-checker's releases.

[email protected]

   🚨 Breaking Changes

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub
Commits
  • 19c58e3 v0.8.0
  • 5179e57 ci: drop changesets, use manual triggered version release
  • fcbb687 fix(ui): use a Vue key so file paths update correctly (#389)
  • aa3d413 feat: advance typescript teminal consolelog text color (#393)
  • 5f5b92a fix(vue-tsc): updated createVueLanguagePlugin syntax, version pin (#398)
  • b2c3236 chore(deps): update dependency @​types/babel__code-frame to ^7.0.6 (#376)
  • 8827a1e chore(deps): update dependency @​types/debug to ^4.1.12 (#377)
  • 152eafb chore(deps): update dependency @​tsconfig/esm to ^1.0.5 (#374)
  • 3a21a23 chore(deps): update dependency @​tsconfig/strictest to ^2.0.5 (#375)
  • 5d01c86 chore(deps): replace dependency npm-run-all with npm-run-all2 ^5.0.0 (#371)
  • Additional commits viewable in compare view

Updates vite-plugin-dts from 4.1.0 to 4.2.3

Release notes

Sourced from vite-plugin-dts's releases.

v4.2.3

Please refer to CHANGELOG.md for details.

v4.2.3-dev.2

Please refer to CHANGELOG.md for details.

v4.2.3-dev.1

Please refer to CHANGELOG.md for details.

v4.2.3-dev.0

Please refer to CHANGELOG.md for details.

v4.2.2

Please refer to CHANGELOG.md for details.

v4.2.1

Please refer to CHANGELOG.md for details.

v4.2.0

Deprecated!

Please refer to CHANGELOG.md for details.

v4.1.1

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite-plugin-dts's changelog.

4.2.3 (2024-09-30)

Bug Fixes

4.2.2 (2024-09-24)

Bug Fixes

  • correctly get package info in pnp mode (984f487), closes #384

4.2.1 (2024-09-08)

Bug Fixes

  • remove api-extractor patch (770d5b1)

4.2.0 (2024-09-08)

Features

4.1.1 (2024-09-06)

Bug Fixes

  • correct resolve Vue when create program (0621332), closes #380
Commits

Updates vitest from 2.0.5 to 2.1.1

Release notes

Sourced from vitest's releases.

v2.1.1

   🐞 Bug Fixes

    View changes on GitHub

v2.1.0

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 vitest-dev/vitest#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

... (truncated)

Commits
  • 699055e chore: release v2.1.1
  • 36b5ace fix(workspace): resolve glob pattern once to avoid name collision (#6489)
  • 16aa76c fix(browser): make example test callbacks async (#6484)
  • 9f1fd18 chore: release v2.1.0
  • 94a186e fix(ui): render project name consistently (#6329)
  • ac698b1 fix: expect.getState().testPath always returns correct path (#6472)
  • b2be23e chore: release v2.1.0-beta.7
  • 0b44722 fix: ignore importer when resolving Vitest (#6469)
  • 97773e2 chore: fix edge case in license files bundling (#6460)
  • 7ab0f4a feat(browser): support --inspect-brk (#6434)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
build(deps-dev): Bump the vite group across 1 directory with 6 updates
d0b15dc 
Bumps the vite group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `4.3.1` | `4.3.2` |
| [@vitest/coverage-istanbul](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-istanbul) | `2.0.5` | `2.1.1` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `5.4.2` | `5.4.8` |
| [vite-plugin-checker](https://github.com/fi3ework/vite-plugin-checker) | `0.7.2` | `0.8.0` |
| [vite-plugin-dts](https://github.com/qmhc/vite-plugin-dts) | `4.1.0` | `4.2.3` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `2.0.5` | `2.1.1` |



Updates `@vitejs/plugin-react` from 4.3.1 to 4.3.2
- [Release notes](https://github.com/vitejs/vite-plugin-react/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite-plugin-react/commits/v4.3.2/packages/plugin-react)

Updates `@vitest/coverage-istanbul` from 2.0.5 to 2.1.1
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v2.1.1/packages/coverage-istanbul)

Updates `vite` from 5.4.2 to 5.4.8
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.4.8/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.4.8/packages/vite)

Updates `vite-plugin-checker` from 0.7.2 to 0.8.0
- [Release notes](https://github.com/fi3ework/vite-plugin-checker/releases)
- [Changelog](https://github.com/fi3ework/vite-plugin-checker/blob/main/CHANGELOG.md)
- [Commits](https://github.com/fi3ework/vite-plugin-checker/compare/[email protected]@0.8.0)

Updates `vite-plugin-dts` from 4.1.0 to 4.2.3
- [Release notes](https://github.com/qmhc/vite-plugin-dts/releases)
- [Changelog](https://github.com/qmhc/vite-plugin-dts/blob/main/CHANGELOG.md)
- [Commits](qmhc/vite-plugin-dts@v4.1.0...v4.2.3)

Updates `vitest` from 2.0.5 to 2.1.1
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v2.1.1/packages/vitest)

---
updated-dependencies:
- dependency-name: "@vitejs/plugin-react"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: vite
- dependency-name: "@vitest/coverage-istanbul"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: vite
- dependency-name: vite
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: vite
- dependency-name: vite-plugin-checker
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: vite
- dependency-name: vite-plugin-dts
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: vite
- dependency-name: vitest
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: vite
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added type: automerge PR will be merged automatically i.e., by a bot or action type: dependencies Maintaining 3rd-party dependencies labels Sep 30, 2024
@dependabot Dependabot
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 7, 2024

Superseded by #3042.

@dependabot dependabot bot closed this Oct 7, 2024
@dependabot dependabot bot deleted the dependabot-npm_and_yarn-vite-8655ec8bb7 branch October 7, 2024 05:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kodiakhq kodiakhq[bot] kodiakhq[bot] approved these changes

Assignees
No one assigned
Labels
type: automerge PR will be merged automatically i.e., by a bot or action type: dependencies Maintaining 3rd-party dependencies
Projects
None yet
Milestone
No milestone
Development

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