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.1.2

Patch Changes

• @linaria/core@8.1.2
• @linaria/react@8.1.2

linaria@8.1.2

Patch Changes

• @linaria/core@8.1.2
• @linaria/react@8.1.2
• @linaria/server@8.1.2

@linaria/postcss-linaria@8.1.2

Patch Changes

• d3b131d: Preserve source escapes within fields changed by fixers

  When a fixer changes part of a selector or declaration value, the stringifier now compares the original and changed CSS escape tokens. Retained source backslashes remain unchanged, while backslashes added by the fixer are still escaped for the surrounding JavaScript template (@linaria/postcss-linaria: fixers double source backslashes in the field they rewrite callstack/linaria#1508).

• c7b0360: Keep comment indentation stable through stylelint --fix

  Indented templates no longer add their base indentation before trailing comments or remove it from continuation lines inside multi-line comments. Repeated parse/stringify passes now preserve both forms byte-for-byte (@linaria/postcss-linaria: stylelint --fix keeps adding whitespace before a trailing comment callstack/linaria#1502).

• cc43835: Fix interpolations and comments being dropped from multi-line selectors and at-rule params

  An interpolation that continues a selector onto the next line looks like a ruleset, so it gets a comment placeholder. PostCSS keeps that comment only in raws.selector.raw, and the re-indented selector was read from selector, so ~ .${styles.parent} came out as ~ . on any stylelint --fix. Multi-line at-rule params had the same problem via raws.params.raw.

  The same defect was fixed for decl.value in the previous release (stylelint --fix drops a trailing interpolation on its own line in a multi-line CSS value callstack/linaria#1494); the selector and params paths were missed. All three now read the raw form through computeCorrectedRawValue.

  Hand-written comments were dropped by the same code path, so a comment inside a multi-line selector or multi-line at-rule params now survives too, interpolations or not.

• ee377a4: Stop stylelint --fix from rewriting templates it should leave alone

  Backslashes inside a template were doubled on the way out and doubled again on every later run (@linaria/postcss-linaria: stylelint --fix repeatedly doubles existing backslashes callstack/linaria#1497). Restored ${...} expressions were passed through the same CSS escaping, so a backtick inside an expression was escaped and could leave the JavaScript unparseable.

  The parser now records each source-derived field before Stylelint rules run. The stringifier leaves backslashes in unchanged fields alone, retains the existing escaping for fields written by fixers, and restores interpolation placeholders only after escaping. The complete JavaScript expression source therefore stays unchanged, and repeated parse/stringify passes are idempotent.

  Fixers can continue to write CSS values with their normal escaping; the stringifier still translates those values into safe JavaScript template source.

• 832c1f8: Preserve source prefixes before interpolations

  The parser now records whether it added a synthetic . or -- to keep an interpolation parseable. The stringifier removes only that recorded marker, so stylelint --fix no longer drops a real leading dot from selectors such as .\${className} (@linaria/postcss-linaria: stylelint --fix drops the leading dot from an interpolated class selector callstack/linaria#1501).

• f3871e6: Fix adjacent interpolations being mangled by stylelint --fix

  substitutePlaceholders split each whitespace-separated token on the placeholder marker and only read the first two parts, so a token holding more than one interpolation — an attribute selector like &[${a}][${b}], or a value like margin: ${a}${b} — silently lost everything from the second interpolation onward, corrupting the output into invalid CSS (@linaria/postcss-linaria: stylelint --fix drops the second interpolati on when several sit in one selector token callstack/linaria#1498).

• d28a5a8: Fix interpolations and indentation being mangled by stylelint --fix

  An interpolation alone on its own line gets a comment placeholder. Inside a parenthesised value PostCSS keeps that comment only in raws.value.raw, and the re-indented value was read from value, so the placeholder was gone by the time the stringifier ran, and the interpolation with it (stylelint --fix drops a trailing interpolation on its own line in a multi-line CSS value callstack/linaria#1494).

  Multi-line at-rule params were corrupted rather than dropped: super.atrule re-reads params through rawValue, so substituting into node.params was discarded and @media screen and ${query} came out as @media screen and .pcss-lin0. An interpolation on the line after the at-rule name lands in the afterName raw and was emitted verbatim for the same reason.

  A newline inside afterName also never had its base indentation restored, so a wrapped at-rule prelude lost its leading whitespace on any fix, templates with no interpolations at all included.

@linaria/react@8.1.2

Patch Changes

• @linaria/core@8.1.2

@linaria/stylelint-config-standard-linaria@8.1.2

Patch Changes

• Updated dependencies [d3b131d]
• Updated dependencies [c7b0360]
• Updated dependencies [cc43835]
• Updated dependencies [ee377a4]
• Updated dependencies [832c1f8]
• Updated dependencies [f3871e6]
• Updated dependencies [d28a5a8]
  • @linaria/postcss-linaria@8.1.2

@linaria/core@8.1.2

@linaria/babel-plugin-interop@8.1.2

@linaria/server@8.1.2

@linaria/stylelint@8.1.2