@vanilla-extract/[email protected]

Patch Changes

• #1627 2fcf8e8 Thanks @stipsan! - Include content in CSS sourcemap when bundling with the extract option

@vanilla-extract/[email protected]

Patch Changes

• #1624 50f1234 Thanks @BPScott! - Include ^7.0.0 in vite dependency range

• Updated dependencies [50f1234]:

  • @vanilla-extract/[email protected]

@vanilla-extract/[email protected]

Minor Changes

• #1604 4a020ba Thanks @drwpow! - Add "extract" option which bundles CSS into one bundle. Removes .css imports.

  EXAMPLE USAGE:

  vanillaExtractPlugin({
    extract: {
      name: 'bundle.css',
      sourcemap: false
    }
  });

@vanilla-extract/[email protected]

Patch Changes

• #1624 50f1234 Thanks @BPScott! - Include ^7.0.0 in vite dependency range

@vanilla-extract/[email protected]

Minor Changes

• #1614 4e92cce Thanks @askoufis! - Add new inlineCssInDev option to unstable_mode configuration property

  Setting unstableMode: 'inlineCssInDev' will result in all CSS generated by Vanilla Extract being inlined into a style element at the top of the document head. This feature is useful for preventing FOUC (Flash of Unstyled Content) when server-rendering your initial HTML. Without this, calling ssrLoadModule on your server entrypoint will not include the CSS in the HTML, leading to a FOUC when the client-side JavaScript takes over.

  Note that CSS will only be inlined in development mode. Production builds are unaffected by this setting.

  EXAMPLE USAGE:

  // vite.config.ts
  import { vanillaExtractPlugin } from '@vanilla-extract/vite-plugin';
  
  export default {
    plugins: [
      vanillaExtractPlugin({
        unstable_mode: 'inlineCssInDev'
      })
    ]
  };

Patch Changes

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

@vanilla-extract/[email protected]

Minor Changes

• #1614 4e92cce Thanks @askoufis! - Add new getAllCss API

  The Compiler class now provides a getAllCss method that returns all the CSS currently stored by the compiler.

  EXAMPLE USAGE:

  import { createCompiler } from '@vanilla-extract/compiler';
  
  const compiler = createCompiler({
    root: process.cwd()
  });
  
  await compiler.processVanillaFile('foo.css.ts');
  await compiler.processVanillaFile('bar.css.ts');
  
  // Contains all CSS created by `foo.css.ts` and `bar.css.ts`
  const allCss = compiler.getAllCss();

@vanilla-extract/[email protected]

Patch Changes

• #1617 f4bd196 Thanks @askoufis! - Don't watch files or invalidate VE modules during SSR

  Fixes a bug where a dependent of a Vanilla Extract module could be evaulated multiple times during ssrLoadModule, potentially causing bugs with singleton variables such as React context.

@vanilla-extract/[email protected]

Patch Changes

• #1610 2b0be1b Thanks @askoufis! - Revert "Improve ESM package entrypoints (#1597)" to fix Named export not found error when importing ESM entrypoints

• Updated dependencies []:

  • @vanilla-extract/[email protected]

@vanilla-extract/[email protected]

Patch Changes

• #1610 2b0be1b Thanks @askoufis! - Revert "Improve ESM package entrypoints (#1597)" to fix Named export not found error when importing ESM entrypoints

• Updated dependencies [2b0be1b]:

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

@vanilla-extract/[email protected]

Patch Changes

• #1610 2b0be1b Thanks @askoufis! - Revert "Improve ESM package entrypoints (#1597)" to fix Named export not found error when importing ESM entrypoints