@vanilla-extract/[email protected]

Major Changes

• #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]

Patch Changes

• Updated dependencies [fdafb6d]:
  • @vanilla-extract/[email protected]

@vanilla-extract/[email protected]

Patch Changes

• #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]

@vanilla-extract/[email protected]

Patch Changes

• #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]

@vanilla-extract/[email protected]

Patch Changes

• #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]

@vanilla-extract/[email protected]

Minor Changes

• #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.

@vanilla-extract/[email protected]

Patch Changes

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

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

@vanilla-extract/[email protected]

Patch Changes

• #1264 e531c41 Thanks @mrm007! - Update dependencies

• Updated dependencies [e531c41, e531c41]:

  • @vanilla-extract/[email protected]

@vanilla-extract/[email protected]

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 as emitCssInSsr has been turned on by default. The emitCssInSsr 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! - The esbuildOptions option has been removed as we are no longer using esbuild internally

• #1264 e531c41 Thanks @mrm007! - Drop support for Vite < 4

Patch Changes

• #1264 e531c41 Thanks @mrm007! - Update dependencies

• Updated dependencies [e531c41, e531c41]:

  • @vanilla-extract/[email protected]

@vanilla-extract/[email protected]

Patch Changes

• #1264 e531c41 Thanks @mrm007! - Update dependencies

• Updated dependencies [e531c41, e531c41]:

  • @vanilla-extract/[email protected]