@vanilla-extract/integration@7.1.3

Patch Changes

• #1388 606660618dc5efa6c529f77cebf9d2b8dc379dbd Thanks @askoufis! - Remove lodash dependency

• #1386 e58cf9013c6f6cdfacb2a7936b3354e71138e9fb Thanks @askoufis! - Replace outdent dependency with dedent

• Updated dependencies [e58cf9013c6f6cdfacb2a7936b3354e71138e9fb, 3df9b4ebc5ad7e03e5c908c10216447b7089132a]:

  • @vanilla-extract/css@1.15.1

@vanilla-extract/css@1.15.1

Patch Changes

• #1386 e58cf9013c6f6cdfacb2a7936b3354e71138e9fb Thanks @askoufis! - Replace outdent dependency with dedent

• #1385 3df9b4ebc5ad7e03e5c908c10216447b7089132a Thanks @askoufis! - Replace chalk dependency with picocolors

@vanilla-extract/css@1.15.0

Minor Changes

• #1379 df9fe3ee3fc0057bc14a2333a405f8229f80c214 Thanks @ronci! - Add support for passing multiple font face rules to globalFontFace

  EXAMPLE USAGE:

  const gentium = 'GlobalGentium';
  
  globalFontFace(gentium, [
    {
      src: 'local("Gentium")',
      fontWeight: 'normal',
    },
    {
      src: 'local("Gentium Bold")',
      fontWeight: 'bold',
    },
  ]);

@vanilla-extract/vite-plugin@4.0.7

Patch Changes

• #1369 05ef2f0 Thanks @askoufis! - Fixes a bug where an internal Remix plugin would throw an error inside the vite-node compiler

• #1368 90f0315 Thanks @askoufis! - Update @vanilla-extract/integration dependency

  This fixes a bug where APIs that used the walkObject utility (e.g. createTheme) would fail when used with module namespace objects inside vite-node. This was due to the previous implementation using the input object's constructor to initialize a clone, which does not work with module namespace objects because they do not have a constructor function.

• Updated dependencies [c8aefe0]:

  • @vanilla-extract/integration@7.1.2

@vanilla-extract/private@1.0.4

Patch Changes

• #1368 90f0315 Thanks @askoufis! - walkObject: Use an empty object to initialize a clone instead of calling the input object's constructor

  This allows walkObject to be used on module namespace objects:

  import { walkObject } from '@vanilla-extract/private';
  import * as ns from './foo';
  
  // Runtime error in `vite-node`
  walkObject(ns, myMappingFunction);

  The previous implementation did not work with these objects because they do not have a constructor function.
  esbuild seems to have papered over this issue by providing a constructor function on these objects, but this seems to not be the case with vite-node, hence the need for this fix.

@vanilla-extract/next-plugin@2.4.0

Minor Changes

• #1365 ed67731 Thanks @renrizzolo! - Pages router: use next-style-loader in dev, output css in ssr

@vanilla-extract/integration@7.1.2

Patch Changes

• #1374 c8aefe0 Thanks @askoufis! - Update @vanilla-extract/css dependency

• Updated dependencies [90f0315]:

  • @vanilla-extract/css@1.14.2

@vanilla-extract/css@1.14.2

Patch Changes

• #1368 90f0315 Thanks @askoufis! - Update @vanilla-extract/private dependency

• Updated dependencies [90f0315]:

  • @vanilla-extract/private@1.0.4

@vanilla-extract/webpack-plugin@2.3.7

Patch Changes

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

@vanilla-extract/vite-plugin@4.0.6

Patch Changes

• #1346 8c2ac42 Thanks @askoufis! - Fix .css.ts file resolution on Windows