Skip to content

Releases: vanilla-extract-css/vanilla-extract

@vanilla-extract/[email protected]

04 Mar 09:28
cff97a7

Choose a tag to compare

Patch Changes

@vanilla-extract/[email protected]

19 Feb 08:33
69d4dc9

Choose a tag to compare

Patch Changes

@vanilla-extract/[email protected]

19 Feb 08:33
69d4dc9

Choose a tag to compare

Patch Changes

@vanilla-extract/[email protected]

09 Feb 04:23
6c65b48

Choose a tag to compare

Patch Changes

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

09 Feb 04:23
6c65b48

Choose a tag to compare

Minor Changes

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

04 Feb 21:10
ec33c1b

Choose a tag to compare

Patch Changes

@vanilla-extract/[email protected]

04 Feb 21:10
ec33c1b

Choose a tag to compare

Patch Changes

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

04 Feb 21:10
ec33c1b

Choose a tag to compare

Patch Changes

@vanilla-extract/[email protected]

04 Feb 21:09
ec33c1b

Choose a tag to compare

Patch Changes

@vanilla-extract/[email protected]

04 Feb 21:09
ec33c1b

Choose a tag to compare

Patch Changes