Skip to content

Commit

Permalink
chore: bump vite from 6.0.1 to 6.0.3 (#977)
Browse files Browse the repository at this point in the history
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.0.1 to 6.0.3.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v6.0.3/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
  • Loading branch information
dependabot[bot] authored Dec 9, 2024
1 parent a95d293 commit a6280a9
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@
"lint-staged": "15.2.10",
"prettier": "3.2.5",
"typescript": "5.6.3",
"vite": "6.0.1",
"vite": "6.0.3",
"vite-plugin-dts": "4.3.0",
"vitest": "2.1.6"
},
Expand Down
8 changes: 4 additions & 4 deletions yarn.lock
Original file line number Diff line number Diff line change
Expand Up @@ -7589,10 +7589,10 @@ [email protected]:
local-pkg "^0.5.0"
magic-string "^0.30.11"

[email protected].1, "vite@^5.0.0 || ^6.0.0":
version "6.0.1"
resolved "https://registry.yarnpkg.com/vite/-/vite-6.0.1.tgz#24c9caf24998f0598de37bed67e50ec5b9dfeaf0"
integrity sha512-Ldn6gorLGr4mCdFnmeAOLweJxZ34HjKnDm4HGo6P66IEqTxQb36VEdFJQENKxWjupNfoIjvRUnswjn1hpYEpjQ==
[email protected].3, "vite@^5.0.0 || ^6.0.0":
version "6.0.3"
resolved "https://registry.yarnpkg.com/vite/-/vite-6.0.3.tgz#cc01f403e326a9fc1e064235df8a6de084c8a491"
integrity sha512-Cmuo5P0ENTN6HxLSo6IHsjCLn/81Vgrp81oaiFFMRa8gGDj5xEjIcEpf2ZymZtZR8oU0P2JX5WuUp/rlXcHkAw==
dependencies:
esbuild "^0.24.0"
postcss "^8.4.49"
Expand Down

0 comments on commit a6280a9

Please sign in to comment.