@vanilla-extract/[email protected]

Patch Changes

• #30 b4591d5 Thanks @mattcompiles! - Fix hash context information not being applied

  This change makes it so all files with a valid CSS file extension (e.g. .css.ts) get hash context information (internally referred to as filescope) applied. This fixes some situations where the "New styles cannot be registered dynamically after initial boot" error would occur incorrectly.

@vanilla-extract/[email protected]

Patch Changes

• #30 b4591d5 Thanks @mattcompiles! - Fix hash context information not being applied

  This change makes it so all files with a valid CSS file extension (e.g. .css.ts) get hash context information (internally referred to as filescope) applied. This fixes some situations where the "New styles cannot be registered dynamically after initial boot" error would occur incorrectly.

• #30 b4591d5 Thanks @mattcompiles! - Ignore compiling files that have already been compiled

@vanilla-extract/[email protected]

Minor Changes

• #20 3311914 Thanks @mattcompiles! - Ensure generated hashes are scoped by package

  vanilla-extract uses file path to ensure unique identifier (e.g. class names, CSS Variables, keyframes, etc) hashes across your application. This information is added to your *.css.ts files at build time. The issue with this approach is it meant *.css.ts files couldn't be pre-compiled when being published to npm.

  This change adds support for pre-compilation of packages by adding package name information to identifier hashes.

Patch Changes

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

@vanilla-extract/[email protected]

Minor Changes

• #20 3311914 Thanks @mattcompiles! - Ensure generated hashes are scoped by package

  vanilla-extract uses file path to ensure unique identifier (e.g. class names, CSS Variables, keyframes, etc) hashes across your application. This information is added to your *.css.ts files at build time. The issue with this approach is it meant *.css.ts files couldn't be pre-compiled when being published to npm.

  This change adds support for pre-compilation of packages by adding package name information to identifier hashes.

• #20 3311914 Thanks @mattcompiles! - Remove projectRoot option in favor of package.json resolution

Patch Changes

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

@vanilla-extract/[email protected]

Minor Changes

• #20 3311914 Thanks @mattcompiles! - Ensure generated hashes are scoped by package

  vanilla-extract uses file path to ensure unique identifier (e.g. class names, CSS Variables, keyframes, etc) hashes across your application. This information is added to your *.css.ts files at build time. The issue with this approach is it meant *.css.ts files couldn't be pre-compiled when being published to npm.

  This change adds support for pre-compilation of packages by adding package name information to identifier hashes.

• #25 c4bedd5 Thanks @markdalgleish! - The createInlineTheme function has now moved to the @vanilla-extract/dynamic package.

  -import { createInlineTheme } from '@vanilla-extract/css/createInlineTheme';
  +import { createInlineTheme } from '@vanilla-extract/dynamic';

@vanilla-extract/[email protected]

Minor Changes

• #20 3311914 Thanks @mattcompiles! - Ensure generated hashes are scoped by package

  vanilla-extract uses file path to ensure unique identifier (e.g. class names, CSS Variables, keyframes, etc) hashes across your application. This information is added to your *.css.ts files at build time. The issue with this approach is it meant *.css.ts files couldn't be pre-compiled when being published to npm.

  This change adds support for pre-compilation of packages by adding package name information to identifier hashes.

• #20 3311914 Thanks @mattcompiles! - Remove projectRoot and alias option

@vanilla-extract/[email protected]

Patch Changes

• #16 ebb3edc Thanks @mattcompiles! - Trigger rebuild for CSS file dependencies