(npm): Bump the vite group with 3 updates #1298
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps the vite group with 3 updates: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite), [vite-node](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vite-node) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `vite` from 5.4.8 to 5.4.9 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v5.4.9/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v5.4.9/packages/vite) Updates `vite-node` from 2.1.2 to 2.1.3 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v2.1.3/packages/vite-node) Updates `vitest` from 2.1.2 to 2.1.3 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v2.1.3/packages/vitest) --- updated-dependencies: - dependency-name: vite dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vite - dependency-name: vite-node dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vite - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-patch dependency-group: vite ... Signed-off-by: dependabot[bot] <support@github.com>
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps the vite group with 3 updates: vite, vite-node and vitest.
Updates
vitefrom 5.4.8 to 5.4.9Changelog
Sourced from vite's changelog.
Commits
898d61frelease: v5.4.9508d9abfix: bump launch-editor-middleware to v2.9.1 (#18348)dc5434cfix(deps): bump tsconfck (#18322)851b258fix(hmr): don't try to rewrite imports for direct CSS soft invalidation (#18252)96084d6fix(data-uri): only match ids starting withdata:(#18241)eae00b5fix(css): fix lightningcss dep url resolution with custom root (#18125)c23558achore: update all url references of vitejs.dev to vite.dev (#18276)1864eb1chore: update license copyright (#18278)ae44163docs: update homepage (#18274)262a879fix(ssr): (backport #18150) fix source map remapping with multiple sources (#...Updates
vite-nodefrom 2.1.2 to 2.1.3Release notes
Sourced from vite-node's releases.
Commits
4c03a0dchore: release v2.1.319d64e2fix(vitest): always inline setup files (#6689)Updates
vitestfrom 2.1.2 to 2.1.3Release notes
Sourced from vitest's releases.
Commits
4c03a0dchore: release v2.1.370baaaafix(vitest): usefast-globinstead oftinyglobbyin Vitest (#6688)19d64e2fix(vitest): always inline setup files (#6689)47dde76fix(vitest): show rollup error details as test error (#6686)7155ceerefactor(coverage): move re-usable parts to base provider (#6665)7a0de0aperf: reuse full name in reported tasks, update generator types (#6666)8bef5d2fix(browser): not.toBeInTheDocument works with locators API (#6634)9ece395fix(vitest): fix\<empty line>logs when interleavingconsole.log/error(#...000459afix(vitest): deprecate old task types and node-reliant types (#6632)946d8bbfix(vitest): don't hang with maxConcurrency 0 (#6627)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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