⬆️ upgrade styled-components to v6.3.8

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
styled-components (source)	6.1.13 → 6.3.8

---

Release Notes

styled-components/styled-components (styled-components)

v6.3.8

Compare Source

Patch Changes

• 55d05c1: Make react-dom an optional peer dependency, clean up some unnecessary type peers.

v6.3.7

Compare Source

Patch Changes

• 51ffa9c: Fix createGlobalStyle compatibility with React StrictMode and RSC

  This fix addresses issues where global styles would disappear or behave incorrectly in React StrictMode and RSC:

  1. Static styles optimization: Static global styles (without props/interpolations) are now only injected once and won't be removed/re-added on every render. This prevents the style flickering that could occur during concurrent rendering.

  2. StrictMode-aware cleanup: Style cleanup now uses queueMicrotask to coordinate with React's effect lifecycle. In StrictMode's simulated unmount/remount cycle, styles are preserved. On real unmount, styles are properly removed.

  3. RSC compatibility: Move useRef inside RSC guard in createGlobalStyle and unify all useContext calls to use consistent !IS_RSC ? pattern.

  4. RSC inline style tag cleanup: Fix bug where server-defined createGlobalStyle rendered in client components would leave behind accumulated SSR-rendered inline <style data-styled-global> tags. The cleanup effect now removes these hoisted style tags when the component unmounts or re-renders with different CSS.

  These changes ensure createGlobalStyle works correctly with:

  • React StrictMode's double-render behavior
  • React 18/19's concurrent rendering features
  • React 19's style hoisting with the precedence attribute
  • React Server Components (server-defined GlobalStyles in client components)

• 51ffa9c: Restore styled.br.

• 1f794b7: Add package.json "exports" field for better native ESM integration.

v6.3.6

Compare Source

Patch Changes

• 189bc17: Fix url() CSS function values being incorrectly stripped when using unquoted URLs containing // (e.g., url(https://example.com)). The // in protocol URLs like https://, http://, file://, and protocol-relative URLs was incorrectly being treated as a JavaScript-style line comment.

v6.3.5

Compare Source

Patch Changes

• 7ff7002: Fix: Line comments (//) in multiline CSS declarations no longer cause parsing errors (fixes #​5613)

  JS-style line comments (//) placed after multiline declarations like calc() were not being properly stripped, causing CSS parsing issues. Comments are now correctly removed anywhere in the CSS while preserving valid syntax.

  Example that now works:

  const Box = styled.div`
    max-height: calc(100px + 200px + 300px); // This comment no longer breaks parsing
    background-color: green;
  `;

• 7ff7002: Fix: Contain invalid CSS syntax to just the affected line

  In styled-components v6, invalid CSS syntax (like unbalanced braces) could cause all subsequent styles to be ignored. This fix ensures that malformed CSS only affects the specific declaration, not subsequent valid styles.

  Example that now works:

  const Circle = styled.div`
    width: 100px;
    line-height: ${() => '14px}'}; // ⛔️ This malformed line is dropped
    background-color: green; // ✅ Now preserved (was ignored in v6)
  `;

v6.3.4

Compare Source

Patch Changes

• 8e8c282: Fixed createGlobalStyle to not use useLayoutEffect on the server, which was causing a warning and broken styles in v6.3.x. The check typeof React.useLayoutEffect === 'function' is not reliable for detecting server vs client environments in React 18+, so we now use the __SERVER__ build constant instead.

v6.3.3

Compare Source

Patch Changes

• 6e4d1e7: fix: suppress false "created dynamically" warnings in React Server Components

  The dynamic creation warning check now properly detects RSC environments and skips validation when IS_RSC is true. This eliminates false warnings for module-level styled components in server components, which were incorrectly flagged due to RSC's different module evaluation context. Module-level styled components in RSC files no longer trigger warnings since they cannot be created inside render functions by definition.

v6.3.2

Compare Source

Patch Changes

• a4b4a6b: fix: include TypeScript declaration files in npm package

  Fixed Rollup TypeScript plugin configuration to override tsconfig.json's noEmit setting, ensuring TypeScript declaration files are generated during build.

• a4b4a6b: fix: resolve TypeScript error blocking type declaration emission

  Fixed TypeScript error in StyledComponent when merging style attributes from attrs. Added explicit type cast to React.CSSProperties to safely merge CSS property objects. This error was preventing TypeScript declaration files from being generated during build.

v6.3.1

Compare Source

Patch Changes

• 046e880: Ensure TypeScript declaration files are included in npm package, needed to tweak a Rollup setting.

v6.3.0

Compare Source

Minor Changes

• 28fd502: Add React Server Components (RSC) support

  styled-components now automatically detects RSC environments and handles CSS delivery appropriately:

  • No 'use client' directive required: Components work in RSC without any wrapper or directive
  • Automatic CSS injection: In RSC mode, styled components emit inline <style> tags that React 19 automatically hoists and deduplicates
  • Zero configuration: Works out of the box with Next.js App Router and other RSC-enabled frameworks
  • Backward compatible: Existing SSR patterns with ServerStyleSheet continue to work unchanged

  RSC best practices:

  • Prefer static styles over dynamic interpolations to avoid serialization overhead
  • Use data attributes for discrete variants (e.g., &[data-size='lg'])
  • CSS custom properties work perfectly in styled-components, can be set via inline style, and cascade to children:

  const Container = styled.div``;
  const Button = styled.button`
    background: var(--color-primary, blue);
  `;
  
  // Variables set on parent cascade to all DOM children
  <Container style={{ '--color-primary': 'orchid' }}>
    <Button>Inherits orchid background</Button>
  </Container>;

  • Use build-time CSS variable generation for theming since ThemeProvider is a no-op in RSC

  Technical details:

  • RSC detection via typeof React.createContext === 'undefined'
  • ThemeProvider and StyleSheetManager become no-ops in RSC (children pass-through)
  • React hooks are conditionally accessed via runtime guards
  • CSS is retrieved from the StyleSheet Tag for inline delivery in RSC mode

• 856cf06: feat: update built-in element aliases to include modern HTML and SVG elements

  Added support for modern HTML and SVG elements that were previously missing:

  HTML elements:

  • search - HTML5 search element
  • slot - Web Components slot element
  • template - HTML template element

  SVG filter elements:

  • All fe* filter primitive elements (feBlend, feColorMatrix, feComponentTransfer, etc.)
  • clipPath, linearGradient, radialGradient - gradient and clipping elements
  • textPath - SVG text path element
  • switch, symbol, use - SVG structural elements

  This ensures styled-components has comprehensive coverage of all styleable HTML and SVG elements supported by modern browsers and React.

Patch Changes

• 418adbe: fix(types): add CSS custom properties (variables) support to style prop

  CSS custom properties (CSS variables like --primary-color) are now fully supported in TypeScript without errors:

  • .attrs({ style: { '--var': 'value' } }) - CSS variables in attrs
  • <Component style={{ '--var': 'value' }} /> - CSS variables in component props
  • Mixed usage with regular CSS properties works seamlessly

• aef2ad6: Update shared css property handling tools to latest versions.

v6.2.0

Compare Source

v6.1.19

Compare Source

Patch Changes

• aa997d8: fix for React Native >=0.79 crashes when using unsupported web-only CSS values (e.g., fit-content, min-content, max-content). The fix emits a warning and ignores the property using those values, instead of causing crashes.

v6.1.18

Compare Source

Patch Changes

• 76b18a4: fix react 19 compatibility
• bdac7af: Quickfix to support expo sdk >= 53 and react-native >=0.79.

v6.1.17

Compare Source

Patch Changes

• 47a4dcb: Fix for loose DefaultTheme type definition
• a8c0f5b: fix: add info link to console

v6.1.16

Compare Source

Patch Changes

• 246c77b: Resolve TS error related to ExoticComponentWithDisplayName API from React.
• 4757191: Native typings weren't on the correct folder, which caused issues on React Native projects using this library

v6.1.15

Compare Source

Patch Changes

• b9688ae: chore: update postcss to version 8.4.49 and nanoid to version 3.3.8

v6.1.14

Compare Source

Patch Changes

• 6908326: Add changesets for release management
• 18ebf6d: Prevent styled() from injecting an undefined ref prop in React 19

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
kitchn-docs	Error		Jan 23, 2026 4:42pm
kitchn-workshop	Error		Jan 23, 2026 4:42pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4103c9d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 3 hours (more than 100, code: "api-deployments-free-per-day").

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 14 hours (more than 100, code: "api-deployments-free-per-day").