Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@linaria/atomic@8.0.0

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
  • @linaria/react@8.0.0

@linaria/core@8.0.0

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.

@linaria/babel-plugin-interop@8.0.0

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.

linaria@8.0.0

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
  • @linaria/react@8.0.0
  • @linaria/server@8.0.0

@linaria/postcss-linaria@8.0.0

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.

@linaria/react@8.0.0

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

@linaria/server@8.0.0

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.

@linaria/stylelint@8.0.0

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.

@linaria/stylelint-config-standard-linaria@8.0.0

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/postcss-linaria@8.0.0

@linaria/testkit@7.0.2

Patch Changes

• Updated dependencies [9d49bef]
  • @linaria/react@8.0.0

linaria-website@6.3.3

Patch Changes

• Updated dependencies [9d49bef]
  • @linaria/atomic@8.0.0
  • @linaria/core@8.0.0
  • @linaria/react@8.0.0
  • @linaria/server@8.0.0