Update vite 5.3.3 → 5.3.4 (patch) #1243
Merged
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ vite (5.3.3 → 5.3.4) · Repo · Changelog
Release Notes
5.3.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
release: v5.3.4
docs(create-vite): add missing tsconfig.app.json file at the project array for react-ts (#17645)
fix(css): include `.css?url` in assets field of manifest (#17623)
refactor: replace includes with logical operations (#17620)
chore: add callback to http-proxy.d.ts jsdoc (#17646)
fix(build): skip preload treeshaking for nested braces (#17687)
fix: update Terser type definitions (fix #17668) (#17669)
chore(deps): update dependency vitest to v2 (#17685)
chore(deps): update dependency @types/picomatch to v3 (#17682)
chore(deps): update dependency eslint-plugin-import-x to v3 (#17683)
chore: add `create-preact` recommendation to Preact templates (#17649)
feat: add `create-preact` to list of options in `create-vite` (#17674)
fix(worker): nested inlined worker always fallbacked to data URI worker instead of using blob worker (#17509)
chore: move shinigami to team emeriti (#17634)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands