chore(deps): update dependency @vanilla-extract/vite-plugin to v4 #2305
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.
This PR contains the following updates:
3.9.5
->4.0.18
Release Notes
vanilla-extract-css/vanilla-extract (@vanilla-extract/vite-plugin)
v4.0.18
Compare Source
Patch Changes
v4.0.17
Compare Source
Patch Changes
1fd348a
Thanks @kube! - Filter outreact-router
Vite plugin when creating thevite-node
compilerv4.0.16
Compare Source
Patch Changes
#1482
30c0305
Thanks @askoufis! - Fixes a bug where Vanilla Extract files with extensions other thancss.ts
were not being invalidated during HMRUpdated dependencies []:
v4.0.15
Compare Source
Patch Changes
96dd466127374b21ad7e48e5dd168a03a96af047
]:v4.0.14
Compare Source
Patch Changes
6668e9e069276b0fd9ccd9668403b4eeb840a11b
,61878f5fb21a33190ef242551c639e216ba4748a
]:v4.0.13
Compare Source
Patch Changes
765b85610207992693a822fb3b1aec995ab48409
Thanks @ArrayKnight! - Fixes a bug where changes to.css.ts
dependencies of top-level.css.ts
files would not generate new CSSv4.0.12
Compare Source
Patch Changes
124c31c2d9fee24d937c4626cec524d527d4e55e
]:v4.0.11
Compare Source
Patch Changes
#1395
8d1731b44f8e93153c8087a533e0f9b2ed99767c
Thanks @askoufis! - Fixes a bug that made the plugin incompatible with frameworks that use custom config filesUpdated dependencies []:
v4.0.10
Compare Source
Patch Changes
#1335
b8a99e4980710a34692034d5da43e584edbc3d17
Thanks @askoufis! - Addtypes
field topackage.json
Updated dependencies [
b8a99e4980710a34692034d5da43e584edbc3d17
]:v4.0.9
Compare Source
Patch Changes
ce738ba9e9a6b5c72cc7868bed724c816ca3cc4e
Thanks @askoufis! - Ensure the compiler instance is re-used between buildsv4.0.8
Compare Source
Patch Changes
#1397
2232ef4aa0b8410ff791626a951a15cc03dfbb09
Thanks @askoufis! - Fixes a bug that was causing output CSS files to not update during watch modeUpdated dependencies [
606660618dc5efa6c529f77cebf9d2b8dc379dbd
,e58cf9013c6f6cdfacb2a7936b3354e71138e9fb
]:v4.0.7
Compare Source
Patch Changes
#1369
05ef2f0
Thanks @askoufis! - Fixes a bug where an internal Remix plugin would throw an error inside thevite-node
compiler#1368
90f0315
Thanks @askoufis! - Update@vanilla-extract/integration
dependencyThis fixes a bug where APIs that used the
walkObject
utility (e.g.createTheme
) would fail when used with module namespace objects insidevite-node
. This was due to the previous implementation using the input object'sconstructor
to initialize a clone, which does not work with module namespace objects because they do not have aconstructor
function.Updated dependencies [
c8aefe0
]:v4.0.6
Compare Source
Patch Changes
8c2ac42
Thanks @askoufis! - Fix.css.ts
file resolution on Windowsv4.0.5
Compare Source
Patch Changes
94d5f06
Thanks @himself65! - Movevite-node
compiler creation to a more appropriate plugin hook to ensure correct cleanup of resourcesv4.0.4
Compare Source
Patch Changes
#1314
e8a6850
Thanks @mrm007! - Resolve and pass a new copy of the Vite config to the vite-node compilerPreviously, we were passing the same Vite config object to the vite-node compiler. This was causing compatibility issues with other plugins, such as Vitest and Remix.
Updated dependencies [
e8a6850
]:v4.0.3
Compare Source
Patch Changes
#1309
fdafb6d
Thanks @mrm007! - Correctly resolve module paths when using Vite plugins that affect module resolution, such asvite-tsconfig-paths
#1308
20e33a5
Thanks @mrm007! - Don't pass Remix Vite plugin to the vite-node compilerRemix throws an error if it's loaded without a config file, which is what we do when we initialise the vite-node compiler.
Updated dependencies [
fdafb6d
]:v4.0.2
Compare Source
Patch Changes
#1304
545bf82
Thanks @fukumasuya! - Pass Viteresolve
config to vite-node compilerThe plugin passes through the project's Vite
resolve
config to the vite-node compiler, which will be used for resolving imports. These options include [resolve.alias
][resolve.alias], [resolve.dedupe
][resolve.dedupe], [resolve.conditions
][resolve.conditions], [resolve.mainFields
][resolve.mainFields], [resolve.extensions
][resolve.extensions], and others.Updated dependencies [
545bf82
]:v4.0.1
Compare Source
Patch Changes
765b85610207992693a822fb3b1aec995ab48409
Thanks @ArrayKnight! - Fixes a bug where changes to.css.ts
dependencies of top-level.css.ts
files would not generate new CSSv4.0.0
Compare Source
Major Changes
#1264
e531c41
Thanks @mrm007! - The Vite plugin now uses a newer, faster, Vite-based compiler by default.The new compiler uses
vite-node
to parse and extract CSS from.css.ts
files. This comes with all the benefits of using Vite, faster builds and the ability to use Vite plugins.The new compiler has been used in Remix ever since support for Vanilla Extract was introduced.
#1264
e531c41
Thanks @mrm007! - The behaviour previously known asemitCssInSsr
has been turned on by default. TheemitCssInSsr
option has been removed.This means that the CSS emitted by the plugin is now processed by Vite, so the plugin no longer needs to resolve PostCSS plugins and process the CSS output itself.
#1264
e531c41
Thanks @mrm007! - TheesbuildOptions
option has been removed as we are no longer using esbuild internally#1264
e531c41
Thanks @mrm007! - Drop support for Vite < 4Patch Changes
#1264
e531c41
Thanks @mrm007! - Update dependenciesUpdated dependencies [
e531c41
,e531c41
]:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.