Skip to content

@linaria/server@8.0.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Jun 18:54
@linaria/server@8.0.0
d715c30
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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.
Assets 2
Loading