Skip to content

Releases: vanilla-extract-css/vanilla-extract

@vanilla-extract/[email protected]

29 Apr 05:30
1381e54

Choose a tag to compare

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/[email protected]

29 Mar 07:06
a623c1c

Choose a tag to compare

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/[email protected]

29 Mar 07:06
a623c1c

Choose a tag to compare

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/[email protected]

29 Mar 07:06
a623c1c

Choose a tag to compare

Minor Changes

@vanilla-extract/[email protected]

29 Mar 07:06
a623c1c

Choose a tag to compare

Patch Changes

@vanilla-extract/[email protected]

29 Mar 07:06
a623c1c

Choose a tag to compare

Patch Changes

@vanilla-extract/[email protected]

09 Mar 06:12
4a54c17

Choose a tag to compare

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/[email protected]

09 Mar 06:12
4a54c17

Choose a tag to compare

Patch Changes

@vanilla-extract/[email protected]

09 Mar 06:12
4a54c17

Choose a tag to compare

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.

  • Updated dependencies [6ac9f66]:

@vanilla-extract/[email protected]

08 Mar 05:08
d333453

Choose a tag to compare

Patch Changes

  • #1353 94d5f06 Thanks @himself65! - Move vite-node compiler creation to a more appropriate plugin hook to ensure correct cleanup of resources