-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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
chore(deps): update dependency @vanilla-extract/vite-plugin to v5 #1533
Conversation
|
Size Change: 0 B Total Size: 539 kB ℹ️ View Unchanged
|
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This PR contains the following updates:
^4.0.2
->^5.0.0
Release Notes
vanilla-extract-css/vanilla-extract (@vanilla-extract/vite-plugin)
v5.0.0
Compare Source
Major Changes
#1537
7810b7c
Thanks @askoufis! - Change the plugin name from"vanilla-extract"
to the more conventional"vite-plugin-vanilla-extract"
#1529
d5b6e70
Thanks @askoufis! - Updatevite
peer dependency range to^5.0.0 || ^6.0.0
BREAKING CHANGE: Vite 4 is no longer supported. Please upgrade to at least Vite 5.
#1537
7810b7c
Thanks @askoufis! - BREAKING CHANGE: User-configured vite plugins are no longer forwarded through to the Vanilla Extract compiler by default. This should not affect most consumers.Previously, all vite plugins except for a select few incompatible plugins were forwarded through. This resulted in a constant game of whack-a-mole as new plugins were added to the list of incompatible plugins as issues were discovered.
Framework-specific plugins, as well as plugins that handle assets and build output, tend not to be relevant to Vanilla Extract code, and in some cases cause more harm than good.
For that reason, in this release only the
vite-tsconfig-paths
plugin is fowarded through by default. This is a relatively common plugin that is know to be compatible with the Vanilla Extract compiler.In most cases users should not need to forward any additional plugins through to the Vanilla Extract compiler. However, if such a case arises, a plugin filter function can be provided via the
unstable_pluginFilter
option:When providing a plugin filter function, the
vite-tsconfig-paths
plugin will no longer be forwarded through by default. If you wish to forward this plugin, you must include it in your filter function.NOTE: The
unstable_pluginFilter
API is considered unstable and may be changed or removed without notice in a future non-major version.Patch Changes
d5b6e70
,d5b6e70
]:v4.0.20
Compare Source
Patch Changes
#1536
a8248be
Thanks @askoufis! - Consume compiler API from new@vanilla-extract/compiler
package instead of@vanilla-extract/integration
Updated dependencies [
5f66abb
,a8248be
,a8248be
,ec0b024
,a8248be
]:v4.0.19
Compare Source
Patch Changes
v4.0.18
Compare Source
Patch Changes
Configuration
📅 Schedule: Branch creation - "* 0-3 1 * *" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.