chore(deps): update dependency vite to v4 #2816
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
4 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#2816
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/vite-4.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
3.2.5
->4.0.1
Release Notes
vitejs/vite
v4.0.1
Compare Source
u
(#11319) (8c0bb7b), closes #11319useDefineForClassFields
value fromtsconfig.compilerOptions.target
(fixes #10296) (# (42976d8), closes #10296 #11301/__open-in-editor
(#11337) (8856c2e), closes #11337@typescript-eslint/ban-ts-comment
(#11326) (e58a4f0), closes #11326v4.0.0
Compare Source
Read the announcement blog post: Announcing Vite 4
Quick links:
Docs in other languages:
Main Changes
This major is smaller in scope compared to Vite 3, with the main objective of upgrading to Rollup 3. We've worked with the ecosystem to ensure a smooth upgrade path for this new major.
Rollup 3
Vite is now using Rollup 3, which allowed us to simplify Vite's internal asset handling and has many improvements. See the Rollup 3 release notes here.
Framework Plugins out of the Vite core monorepo
@vitejs/plugin-vue
and@vitejs/plugin-react
have been part of Vite core monorepo since the first versions of Vite. This helped us to get a close feedback loop when making changes as we were getting both Core and the plugins tested and released together. With vite-ecosystem-ci we can get this feedback with these plugins developed on independent repositories, so from Vite 4, they have been moved out of the Vite core monorepo. This is meaningful for Vite's framework-agnostic story, and will allow us to build independent teams to maintain each of the plugins. If you have bugs to report or features to request, please create issues on the new repositories moving forward:vitejs/vite-plugin-vue
andvitejs/vite-plugin-react
.New React plugin using SWC during development
SWC is now a mature replacement for Babel, especially in the context of React projects. SWC's React Fast Refresh implementation is a lot faster than Babel, and for some projects, it is now a better alternative. From Vite 4, two plugins are available for React projects with different tradeoffs. We believe that both approaches are worth supporting at this point, and we'll continue to explore improvements to both plugins in the future.
@vitejs/plugin-react
@vitejs/plugin-react is a plugin that uses esbuild and Babel, achieving fast HMR with a small package footprint and the flexibility of being able to use the babel transform pipeline.
@vitejs/plugin-react-swc (new)
@vitejs/plugin-react-swc is a new plugin that uses esbuild during build, but replaces Babel with SWC during development. For big projects that don't require non-standard React extensions, cold start and Hot Module Replacement (HMR) can be significantly faster.
Compatibility
The modern browser build now targets
safari14
by default for wider ES2020 compatibility (https://github.com/vitejs/vite/issues/9063). This means that modern builds can now useBigInt
and that the nullish coallessing operator isn't transpiled anymore. If you need to support older browsers, you can add@vitejs/plugin-legacy
as usual.Importing CSS as a string
In Vite 3, importing the default export of a
.css
file could introduce a double loading of CSS.This double loading could occur since a
.css
file will be emitted and it's likely that the CSS string will also be used by the application code — for example, injected by the framework runtime. From Vite 4, the.css
default export has been deprecated. The?inline
query suffix modifier needs to be used in this case, as that doesn't emit the imported.css
styles.Other features
kB
to align with browser dev tools (#10982)Features
expand
(#11141) (825c793), closes #11141safari14
by default for wider ES2020 compatibility (#9063) (3cc65d7), closes #9063transformIndexHtml
hook (#9669) (1db52bf), closes #9669Bug Fixes
\0
to virtual files id (#11261) (02cdfa9), closes #11261NODE_ENV
more predictable (#10996) (8148af7), closes #10996addWatchFile()
work (fix #7024) (#9723) (34db08b), closes #7024 #9723null
fromCSSModulesOptions.localsConvention
(#10904) (a9978dd), closes #10904base
inresolveConfig
and dev server (#10247) (16e4123), closes #10247Previous Changelogs
4.0.0-beta.7 (2022-12-08)
See 4.0.0-beta.7 changelog
4.0.0-beta.6 (2022-12-08)
See 4.0.0-beta.6 changelog
4.0.0-beta.5 (2022-12-08)
See 4.0.0-beta.5 changelog
4.0.0-beta.4 (2022-12-07)
See 4.0.0-beta.4 changelog
4.0.0-beta.3 (2022-12-07)
See 4.0.0-beta.3 changelog
4.0.0-beta.2 (2022-12-07)
See 4.0.0-beta.2 changelog
4.0.0-beta.1 (2022-12-06)
See 4.0.0-beta.1 changelog
4.0.0-beta.0 (2022-12-05)
See 4.0.0-beta.0 changelog
4.0.0-alpha.6 (2022-11-30)
See 4.0.0-alpha.6 changelog
4.0.0-alpha.5 (2022-11-22)
See 4.0.0-alpha.5 changelog
4.0.0-alpha.4 (2022-11-17)
See 4.0.0-alpha.4 changelog
4.0.0-alpha.3 (2022-11-15)
See 4.0.0-alpha.3 changelog
4.0.0-alpha.2 (2022-11-13)
See 4.0.0-alpha.2 changelog
4.0.0-alpha.1 (2022-11-12)
See 4.0.0-alpha.1 changelog
4.0.0-alpha.0 (2022-11-07)
See 4.0.0-alpha.0 changelog
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
Hi renovate!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://2816-renovate-vite-4-x--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
4047fa50c2
to32d6a8a785
32d6a8a785
to85e895f989
I wonder why the tests fail - the port seems to be correct but all accesses to it seem to return 404
85e895f989
to173e1a359f
173e1a359f
to659fd152c8
659fd152c8
to642335da27
I tried this out locally. Everything seemed to work
642335da27
to3f316c82a5
3f316c82a5
to408e6854b4
408e6854b4
tod73ab76d4a
d73ab76d4a
toa86a6dad94
a86a6dad94
to5f92810bc9
5f92810bc9
to76651ca50b
76651ca50b
to36da6dfe30
36da6dfe30
to3723ebf58d