@vanilla-extract/[email protected]

Patch Changes

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

@vanilla-extract/[email protected]

Patch Changes

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

@vanilla-extract/[email protected]

Patch Changes

• #1545 965fd03 Thanks @askoufis! - Extend esbuild dependency range to include 0.25.x

• Updated dependencies [965fd03]:

  • @vanilla-extract/[email protected]

@vanilla-extract/[email protected]

Patch Changes

• #1545 965fd03 Thanks @askoufis! - Extend esbuild dependency range to include 0.25.x

@vanilla-extract/[email protected]

Patch Changes

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

@vanilla-extract/[email protected]

Patch Changes

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

@vanilla-extract/[email protected]

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! - Update vite 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:

  // vite.config.ts
  
  import { vanillaExtractPlugin } from '@vanilla-extract/vite-plugin';
  import { vitePluginFoo } from 'vite-plugin-foo';
  
  export default defineConfig({
    plugins: [
      vitePluginFoo(),
      vanillaExtractPlugin({
        // Only forward the `vite-plugin-foo` plugin through to the Vanilla Extract compiler
        unstable_pluginFilter: ({ name, mode }) =>
          plugin.name === 'vite-plugin-foo'
      })
    ]
  });

  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

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

@vanilla-extract/[email protected]

Patch Changes

• #1529 d5b6e70 Thanks @askoufis! - Update vite-node dependency

• #1529 d5b6e70 Thanks @askoufis! - Include ^6.0.0 in vite dependency range

@vanilla-extract/[email protected]

Patch Changes

• Updated dependencies [5f66abb, a8248be, ec0b024, a8248be]:
  • @vanilla-extract/[email protected]

@vanilla-extract/[email protected]

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

  • @vanilla-extract/[email protected]
  • @vanilla-extract/[email protected]