Update Linaria packages (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@linaria/core	^6.3.0 → ^8.0.0
@linaria/react	^6.3.0 → ^8.0.0
@linaria/stylelint-config-standard-linaria	^6.2.0 → ^8.0.0
@wyw-in-js/babel-preset	^0.6.0 → ^2.0.0
@wyw-in-js/webpack-loader	^0.6.0 → ^2.0.0

---

Release Notes

callstack/linaria (@​linaria/core)

v8.2.0

Compare Source

Minor Changes

• dcc996a: Update WyW dependencies to 2.4.0.

Patch Changes

• 0ddc4d6: Declare built-in WyW semantics for the css and styled processors so static processor values can be resolved without evaluating their modules. Atomic styled uses the same target semantics, while atomic css keeps its post-extraction JS contract.

v8.1.1

Compare Source

Patch Changes

• 08bb5fd: Reduce TypeScript memory usage for polymorphic as props while preserving intrinsic element prop inference.
  • @​linaria/core@8.1.1

v8.1.0

Compare Source

Minor Changes

• 63840d6: Update WyW dependencies to 2.1.5.

Patch Changes

• 45539fd: Remove package dependencies that are no longer used by Linaria.
• 7764719: Omit dynamic CSS custom properties when a runtime interpolation returns null or undefined.
• be435e4: Increase selector specificity when styling React.lazy targets so wrapper styles can override lazy-loaded component CSS.
• 74a417b: Add typing for intrinsic props selected through the polymorphic as prop on styled components.
• Updated dependencies [45539fd]
• Updated dependencies [63840d6]
  • @​linaria/core@8.1.0

v8.0.0

Compare Source

Major Changes

• 9d49bef: Release Linaria 8 with WyW 2.x stable dependencies and Node.js 22.12+ support.

  Linaria processors now expose WyW 2 static evaluation semantics, allowing the default eval.strategy: "hybrid" mode to resolve statically provable values before falling back to the evaluator. This keeps existing dynamic/runtime-only interpolation support while reducing evaluator work for values that can be resolved from static bindings and imports.

  Performance and stability:

  With the default hybrid mode, a large share of style computation now moves out of runtime-like evaluator execution and into analytical static evaluation. This reduces evaluator startup and module execution work, makes builds less sensitive to runtime-only side effects, and gives the pipeline a more stable foundation for further optimization. It also opens the path for substantially larger speedups as WyW moves more of the pipeline to Rust; see the WyW roadmap for more detail.

  Migration notes:

  • Node.js 22.12 or newer is required.
  • @wyw-in-js/transform is updated to 2.0.2 to avoid duplicate CSS emitted for same-file processor bindings referenced from another processor template inside a local scope and to keep mixed static/processor object-member interpolations statically resolvable.
  • Top-level evaluate config should be migrated to eval.strategy. Use execute for evaluator-only compatibility, keep the default hybrid for static-first resolution with fallback, or use static to reject evaluator fallback.
  • Babel config and Babel resolver plugins are no longer used as an implicit module-resolution fallback during WyW evaluation. Move build-time alias handling to WyW configuration with eval.customResolver, eval.resolver, or staticBindings.
  • CSS rule emission order may change for cascade ties with identical specificity because WyW 2 uses the Oxc/static-first pipeline and can preserve/process imports differently. Make precedence explicit with selector specificity, composition, or source structure where order matters.

Patch Changes

• Updated dependencies [9d49bef]
  • @​linaria/core@8.0.0

v7.0.0

Compare Source

Major Changes

• ab11ebb: BREAKING: bump @wyw-in-js/* dependencies to ^1.0.0 (stable).

  This release updates Linaria's build-time evaluation engine (WyW). See https://wyw-in-js.dev/stability for practical guidance and common pitfalls.

  Notes:

  • Linaria 7 requires Node.js 20+ (aligned with WyW 1.x).
  • If you import JSON from code that is evaluated by WyW, add .json to extensions and ensure .json is ignored by evaluation rules (so it's parsed as JSON, not by Babel).
  • Rollup users: WyW 1.x serializes transform() by default (serializeTransform: true). If you hit Rollup "Unexpected early exit" (unresolved plugin promises / deadlock during resolve), set serializeTransform: false (see examples/rollup/rollup.config.mjs).
  • WyW 1.x promotes fully-statically-evaluatable modules to only: ['*'] and can re-evaluate modules when cached exports are incomplete (cached export values might not be reused).

wyw-in-js/wyw-in-js (@​wyw-in-js/babel-preset)

v2.5.1

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.5.1

v2.5.0

Compare Source

Minor Changes

• Bump versions

Patch Changes

• Updated dependencies
  • @​wyw-in-js/shared@2.5.0
  • @​wyw-in-js/transform@2.5.0

v2.4.4

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.4.4

v2.4.3

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.4.3

v2.4.2

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.4.2

v2.4.1

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.4.1

v2.4.0

Compare Source

Minor Changes

• Bump versions

Patch Changes

• Updated dependencies
  • @​wyw-in-js/shared@2.4.0
  • @​wyw-in-js/transform@2.4.0

v2.3.1

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.3.1

v2.3.0

Compare Source

Minor Changes

• Bump versions

Patch Changes

• Updated dependencies
  • @​wyw-in-js/shared@2.3.0
  • @​wyw-in-js/transform@2.3.0

v2.2.0

Compare Source

Minor Changes

• Bump versions

Patch Changes

• Updated dependencies
  • @​wyw-in-js/shared@2.2.0
  • @​wyw-in-js/transform@2.2.0

v2.1.6

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.1.6

v2.1.5

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.1.5

v2.1.4

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.1.4

v2.1.3

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.1.3

v2.1.2

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.1.2

v2.1.1

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.1.1

v2.1.0

Compare Source

Minor Changes

• Bump versions

Patch Changes

• Updated dependencies
  • @​wyw-in-js/shared@2.1.0
  • @​wyw-in-js/transform@2.1.0

v2.0.2

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.0.2

v2.0.1

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@2.0.1

v2.0.0

Compare Source

Major Changes

• Align private workspace packages and examples for v2.

v1.1.0

Compare Source

Minor Changes

• 69004e7: Add a supported processor diagnostics seam that lets library-owned processors emit structured non-fatal warnings through WyW.

  This adds:

  • BaseProcessor.addDiagnostic() and typed diagnostics helpers in @wyw-in-js/processor-utils
  • normalized diagnostics output from @wyw-in-js/transform
  • diagnostics reporting in @wyw-in-js/vite and @wyw-in-js/cli

  Existing hard failures and metadata sidecar behavior stay intact.

• 69004e7: Add opt-in metadata manifest plumbing across @wyw-in-js/shared, @wyw-in-js/transform, @wyw-in-js/vite, and @wyw-in-js/cli.

  When outputMetadata is enabled:

  • @wyw-in-js/transform now returns normalized, public metadata alongside the existing transform result.
  • @wyw-in-js/vite emits .wyw-in-js.json sidecar assets during build.
  • @wyw-in-js/cli writes matching .wyw-in-js.json sidecar files and supports an --output-metadata flag.

  This keeps default JS/CSS output unchanged while exposing a stable manifest path for library-owned tooling.

Patch Changes

• Updated dependencies
  • @​wyw-in-js/shared@1.1.0
  • @​wyw-in-js/transform@1.1.0

v1.0.8

Compare Source

Patch Changes

• ba60b51: Add Vite 8 support without dropping Vite 5-7 compatibility, and fix destructured binding evaluation in @wyw-in-js/transform on newer Babel versions.
• Updated dependencies
  • @​wyw-in-js/transform@1.0.8

v1.0.7

Compare Source

v1.0.6

Compare Source

Patch Changes

• Updated dependencies
  • @​wyw-in-js/transform@1.0.6

v1.0.5

Compare Source

Patch Changes

• 3dec017: Fix cache invalidation storms when loader-provided code differs from filesystem code, keep the Vite resolver stable across repeated configResolved calls, and avoid eagerly walking dynamic import targets during eval-only runs (prevents action handler is already set and improves build performance on large projects).

• a936749: Drop Node.js <20 support (Node 18 is EOL).

  Note: WyW 1.0.0 already effectively required Node 20 in practice; this change makes the support policy explicit and
  aligns docs/CI accordingly.

  If DOM emulation is enabled (features.happyDOM), but happy-dom cannot be loaded via require() (ESM-only), WyW will
  fall back to running without DOM and print a one-time warning with guidance.

• 9e08238: Fix cache invalidation when a file is first read from the filesystem and later provided by a bundler/loader, preventing stale transforms and related Vite build/dev issues.

• ed6a3e6: Fix a Vite dev error ("action handler is already set") by isolating WyW transform cache per plugin context.

• Updated dependencies

  • @​wyw-in-js/shared@1.0.4
  • @​wyw-in-js/transform@1.0.5

v1.0.4

Compare Source

Patch Changes

• b3bc127: Fix async module resolution by calling the bundler resolve() with the correct plugin context.
• Updated dependencies
  • @​wyw-in-js/shared@1.0.3
  • @​wyw-in-js/transform@1.0.4

v1.0.3

Compare Source

Patch Changes

• adbd48c: Avoid falling back to Node resolution for Vite external resolved file ids (incl. external: "absolute"), which could break aliased imports during build-time evaluation (SSR/dev).
• Updated dependencies
  • @​wyw-in-js/transform@1.0.3

v1.0.2

Compare Source

Patch Changes

• Bump versions

v1.0.1

Compare Source

Patch Changes

• Bump versions

v1.0.0

Compare Source

Major Changes

• 94c5efa: Release 1.0.0 introduces no breaking changes compared to previous releases.

  This release establishes a stable baseline for future development, including upcoming releases focused on performance
  and build-time optimizations.

v0.8.1

Compare Source

Patch Changes

• fcfdf52: Avoid infinite recursion when encountering import cycles while invalidating the cache.

v0.8.0

Compare Source

Minor Changes

• Bump versions

v0.7.0

Compare Source

Minor Changes

• 168341b: New option prefixer that allows disabling the built-in CSS-prefixed.
• 58da575: Ensure cache invalidates correctly when dependency content changes.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.74%. Comparing base (0690a40) to head (15d1402).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #501   +/-   ##
=======================================
  Coverage   95.74%   95.74%           
=======================================
  Files           6        6           
  Lines          47       47           
  Branches        9        9           
=======================================
  Hits           45       45           
  Misses          2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.