vanilla-extract

#1333 6ac9f66 Thanks @askoufis! - Use a more accurate regex for detecting webpack template strings in paths

We now use a modified version of the regex from the webpack source code to detect template strings in paths.
As long as the path isn't already escaped, we should detect it.

Updated dependencies [6ac9f66]:

• @vanilla-extract/[email protected]

#1319 6f7f738 Thanks @joeldavuk! - Update Babel dependencies to address https://github.com/advisories/GHSA-67hx-6x53-jw92

Updated dependencies [6f7f738]:

• @vanilla-extract/[email protected]

#1314 e8a6850 Thanks @mrm007! - Resolve and pass a new copy of the Vite config to the vite-node compiler

Previously, 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]:

• @vanilla-extract/[email protected]

#1314 e8a6850 Thanks @mrm007! - A Vite config object can be passed to the vite-node compiler via the viteConfig option

viteResolve and vitePlugins options are deprecated and will be removed in a future version.

• @vanilla-extract/[email protected]

#1309 fdafb6d Thanks @mrm007! - Correctly resolve module paths when using Vite plugins that affect module resolution, such as vite-tsconfig-paths

#1308 20e33a5 Thanks @mrm007! - Don't pass Remix Vite plugin to the vite-node compiler

Remix 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]:

• @vanilla-extract/[email protected]

• @vanilla-extract/[email protected]

#1309 fdafb6d Thanks @mrm007! - Use absolute paths internally to make sure Vite resolves modules correctly

This change only affects integrations that use the vite-node compiler, which is currently the esbuild (next) and Vite plugins

• @vanilla-extract/[email protected]

• @vanilla-extract/[email protected]

• @vanilla-extract/[email protected]

#1247 f0c3be9 Thanks @askoufis! - Fixes a bug that was causing style compilation to fail on paths containing webpack template strings such as [id] or Next.js dynamic routes such as [slug].

Updated dependencies [545bf82]:

• @vanilla-extract/[email protected]

#1247 f0c3be9 Thanks @askoufis! - Fixes a bug that was causing style compilation to fail on paths containing webpack template strings such as [id] or Next.js dynamic routes such as [slug].

Updated dependencies [f0c3be9]:

• @vanilla-extract/[email protected]

#1304 545bf82 Thanks @fukumasuya! - Pass Vite resolve config to vite-node compiler

The 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.dedupe, resolve.conditions, resolve.mainFields, resolve.extensions, and others.

Updated dependencies [545bf82]:

• @vanilla-extract/[email protected]

#1304 545bf82 Thanks @fukumasuya! - Add a viteResolve option to the vite-node compiler

This allows integrations to provide a Vite resolve config to the vite-node compiler, which will be used for resolving imports. These options include resolve.alias, resolve.dedupe, resolve.conditions, resolve.mainFields, resolve.extensions, and others.

#1300 d0b84f6 Thanks @mrm007! - Skip loading plugins added by Vitest

#1297 85e1131 Thanks @mrm007! - Correctly resolve the user's Vite plugins

#1264 e531c41 Thanks @mrm007! - Update dependencies

Updated dependencies [e531c41, e531c41]:

• @vanilla-extract/[email protected]