You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
db4f940: Fix test performance regression in 6.3.x by eliminating double style rendering in createGlobalStyle and removing unnecessary DOM queries during cleanup in client/test environments.
1203f80: Fix React Native crash caused by document references in the native build. The native bundle no longer includes DOM code, resolving compatibility with RN 0.79+ and Hermes.
5ef3804: Gracefully handle CSS syntax errors in React Native instead of crashing. Missing semicolons and other syntax issues now log a warning in development and produce an empty style object instead of throwing a fatal error.
a777f5a: Preserve explicitly passed undefined props instead of stripping them. This fixes compatibility with libraries like MUI and Radix UI that pass undefined to reset inherited defaults (e.g., role={undefined}). Props set to undefined via .attrs() are still stripped as before.
ca61aca: Fix CSS block comments containing // (e.g. URLs) causing subsequent styles to not be applied.
a2cd792: Fix createGlobalStyle styles not being removed when unmounted in RSC environments. React 19's precedence attribute on style tags makes them persist as permanent resources; global styles now render without precedence so they follow normal component lifecycle.
dbe0aae: In RSC environments, theme is now undefined instead of {} for styled components, matching the existing behavior of withTheme and createGlobalStyle. This ensures accessing theme properties without a ThemeProvider correctly throws rather than silently returning undefined.
1888c73: Fix withTheme HOC types: ref now correctly resolves to the component instance type instead of the constructor, and theme is properly optional in the wrapped component's props.
f84f3fa: Fix SSR styles hydration and global style cleanup in Shadow DOM
43a5b4b: Optimize internal style processing hot paths: cached GroupedTag index lookups, string fast path in flatten, direct string concatenation in dynamic style generation, pre-built stylis middleware chain with lazy RegExp creation, single-lookup Map operations, VirtualTag append fast-path, and manual string concat in SSR output.
788e8c0: Revert exports field and restore browser/server build split with browser field in package.json. Fixes require('stream') resolution errors in browser bundlers like webpack 5.
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:
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.
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.
RSC compatibility: Move useRef inside RSC guard in createGlobalStyle and unify all useContext calls to use consistent !IS_RSC ? pattern.
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)
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.
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:
constBox=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:
constCircle=styled.div` width: 100px; line-height: ${()=>'14px}'}; // ⛔️ This malformed line is dropped background-color: green; // ✅ Now preserved (was ignored in v6)`;
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.
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.
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.
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:
constContainer=styled.div``;constButton=styled.button` background: var(--color-primary, blue);`;// Variables set on parent cascade to all DOM children<Containerstyle={{'--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:
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.
Review the following alerts detected in dependencies.
According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
Action
Severity
Alert (click "▶" to expand/collapse)
Warn
License policy violation: npm typescript
License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/typescript@5.9.3. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.1.1→^1.3.3^1.3.0→^1.3.2^2.1.0→^2.1.8^2.1.1→^2.2.6^1.2.0→^1.3.6^1.0.3→^1.0.66.1.18-canary.4→6.1.24^22.1.0→^22.19.15^18.3.12→^18.3.28^18.3.1→^18.3.7^0.7.0→^0.7.1^4.0.1→^4.0.2^7.0.0→^7.1.0^8.4.49→^8.5.8^0.6.8→^0.7.26.1.18→6.3.12^2.4.0→^2.6.1^3.4.14→^3.4.195.6.3→5.9.3Release Notes
radix-ui/primitives (@radix-ui/react-checkbox)
v1.2.3v1.2.2v1.2.1v1.2.0v1.1.5Compare Source
v1.1.4Compare Source
v1.1.3Compare Source
sanity-io/prettier-config (@sanity/prettier-config)
v1.0.6Compare Source
Bug Fixes
v1.0.5Compare Source
Bug Fixes
v1.0.4Compare Source
Bug Fixes
sanity-io/styled-components-last-resort (@sanity/styled-components)
v6.1.24Compare Source
Patch Changes
b5a916eThanks @renovate! - fix(deps): Update dependency csstype to v3.2.3v6.1.23Compare Source
Patch Changes
0b16591Thanks @renovate! - fix(deps): Update dependency @emotion/is-prop-valid to v1.4.0v6.1.22Compare Source
Patch Changes
f52de1fThanks @stipsan! - GitHub repo renamedv6.1.21Compare Source
Patch Changes
551f1e3Thanks @stipsan! - Update READMEv6.1.19Compare Source
Patch Changes
db218deThanks @stipsan! - Add support for setting SC_ATTR with process.env.SANITY_SC_ATTRv6.1.18Patch Changes
284e925Thanks @renovate! - chore(deps): update dependency rollup to ^4.49.0joe-bell/cva (class-variance-authority)
v0.7.1Compare Source
What's Changed
New Contributors
Full Changelog: joe-bell/cva@v0.7.0...v0.7.1
Evercoder/culori (culori)
v4.0.2Compare Source
Bug fixes
css-color-4spec (#237, #249, #255)toGamut()throws a more useful error than simply crashing thenmodecolor space does not have lightness and chroma components (#261)lab/lch/lab65/lch65to match CSS spec (#260)krisk/Fuse (fuse.js)
v7.1.0Compare Source
Features
Bug Fixes
parseIndex(72b6e25), closes #524 #624parseIndex(78c628e), closes #524 #624postcss/postcss (postcss)
v8.5.8Compare Source
Processor#version.v8.5.7Compare Source
v8.5.6Compare Source
ContainerWithChildrentype discriminating (by @Goodwine).v8.5.5Compare Source
package.json→exportscompatibility with some tools (by @JounQin).v8.5.4Compare Source
v8.5.3Compare Source
Unknown worderror (by @hiepxanh).v8.5.2Compare Source
v8.5.1Compare Source
v8.5.0: 8.5 “Duke Alloces”Compare Source
PostCSS 8.5 brought API to work better with non-CSS sources like HTML, Vue.js/Svelte sources or CSS-in-JS.
@romainmenke during his work on Stylelint added
Input#documentin additional toInput#css.Thanks to Sponsors
This release was possible thanks to our community.
If your company wants to support the sustainability of front-end infrastructure or wants to give some love to PostCSS, you can join our supporters by:
tailwindlabs/prettier-plugin-tailwindcss (prettier-plugin-tailwindcss)
v0.7.2Compare Source
Fixed
prettier-plugin-sveltewhen using Prettier v3.7+ (#418)v0.7.1Compare Source
Fixed
v0.7.0Compare Source
Added
@source,@plugin, and@config(#387)Changed
ParserOptionsandRequiredOptionstypes (#354)prettier-plugin-import-sort(#385)Fixed
@apply(#392)v0.6.14Compare Source
v0.6.13Compare Source
prettier-plugin-multiline-arraysandprettier-plugin-jsdocwork when used together with this plugin (#372)v0.6.12Compare Source
v0.6.11Compare Source
v0.6.10Compare Source
@zackad/prettier-plugin-twig(#327)@zackad/prettier-plugin-twig-melody(#327)v0.6.9Compare Source
tailwindStylesheetoption to replacetailwindEntryPoint(#330)styled-components/styled-components (styled-components)
v6.3.12Compare Source
Patch Changes
db4f940: Fix test performance regression in 6.3.x by eliminating double style rendering increateGlobalStyleand removing unnecessary DOM queries during cleanup in client/test environments.1203f80: Fix React Native crash caused bydocumentreferences in the native build. The native bundle no longer includes DOM code, resolving compatibility with RN 0.79+ and Hermes.5ef3804: Gracefully handle CSS syntax errors in React Native instead of crashing. Missing semicolons and other syntax issues now log a warning in development and produce an empty style object instead of throwing a fatal error.a777f5a: Preserve explicitly passedundefinedprops instead of stripping them. This fixes compatibility with libraries like MUI and Radix UI that passundefinedto reset inherited defaults (e.g.,role={undefined}). Props set toundefinedvia.attrs()are still stripped as before.v6.3.11Compare Source
Patch Changes
752f5ec: fix: resolve "React is not defined" ReferenceError introduced in 6.3.10 when loading the CJS build in Node.jsv6.3.10Compare Source
Patch Changes
f674224: fix: RSC style tags for extended components have correct href and include base CSS (#5663)<style href>attribute that caused React 19 hydration failures when usingstyled()inheritance<style>tag per inheritance level with content-aware hrefs, enabling React 19 deduplication of shared base stylesf674224: Reduce standalone/browser bundle size by making IS_RSC a build-time constant, enabling dead code elimination of RSC-specific branchesv6.3.9Compare Source
Patch Changes
ca61aca: Fix CSS block comments containing//(e.g. URLs) causing subsequent styles to not be applied.a2cd792: FixcreateGlobalStylestyles not being removed when unmounted in RSC environments. React 19'sprecedenceattribute on style tags makes them persist as permanent resources; global styles now render withoutprecedenceso they follow normal component lifecycle.dbe0aae: In RSC environments,themeis nowundefinedinstead of{}for styled components, matching the existing behavior ofwithThemeandcreateGlobalStyle. This ensures accessing theme properties without a ThemeProvider correctly throws rather than silently returningundefined.1888c73: FixwithThemeHOC types: ref now correctly resolves to the component instance type instead of the constructor, andthemeis properly optional in the wrapped component's props.f84f3fa: Fix SSR styles hydration and global style cleanup in Shadow DOM43a5b4b: Optimize internal style processing hot paths: cached GroupedTag index lookups, string fast path in flatten, direct string concatenation in dynamic style generation, pre-built stylis middleware chain with lazy RegExp creation, single-lookup Map operations, VirtualTag append fast-path, and manual string concat in SSR output.788e8c0: Revertexportsfield and restore browser/server build split withbrowserfield in package.json. Fixesrequire('stream')resolution errors in browser bundlers like webpack 5.v6.3.8Compare Source
Patch Changes
55d05c1: Make react-dom an optional peer dependency, clean up some unnecessary type peers.v6.3.7Compare Source
Patch Changes
51ffa9c: Fix createGlobalStyle compatibility with React StrictMode and RSCThis fix addresses issues where global styles would disappear or behave incorrectly in React StrictMode and RSC:
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.
StrictMode-aware cleanup: Style cleanup now uses
queueMicrotaskto coordinate with React's effect lifecycle. In StrictMode's simulated unmount/remount cycle, styles are preserved. On real unmount, styles are properly removed.RSC compatibility: Move
useRefinside RSC guard increateGlobalStyleand unify alluseContextcalls to use consistent!IS_RSC ?pattern.RSC inline style tag cleanup: Fix bug where server-defined
createGlobalStylerendered 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
createGlobalStyleworks correctly with:precedenceattribute51ffa9c: Restorestyled.br.1f794b7: Add package.json "exports" field for better native ESM integration.v6.3.6Compare 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 likehttps://,http://,file://, and protocol-relative URLs was incorrectly being treated as a JavaScript-style line comment.v6.3.5Compare 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 likecalc()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:
7ff7002: Fix: Contain invalid CSS syntax to just the affected lineIn 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:
v6.3.4Compare Source
Patch Changes
8e8c282: FixedcreateGlobalStyleto not useuseLayoutEffecton the server, which was causing a warning and broken styles in v6.3.x. The checktypeof 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.3Compare Source
Patch Changes
6e4d1e7: fix: suppress false "created dynamically" warnings in React Server ComponentsThe dynamic creation warning check now properly detects RSC environments and skips validation when
IS_RSCis 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.2Compare Source
Patch Changes
a4b4a6b: fix: include TypeScript declaration files in npm packageFixed 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 emissionFixed 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.1Compare Source
Patch Changes
046e880: Ensure TypeScript declaration files are included in npm package, needed to tweak a Rollup setting.v6.3.0Compare Source
Minor Changes
28fd502: Add React Server Components (RSC) supportstyled-components now automatically detects RSC environments and handles CSS delivery appropriately:
'use client'directive required: Components work in RSC without any wrapper or directive<style>tags that React 19 automatically hoists and deduplicatesServerStyleSheetcontinue to work unchangedRSC best practices:
&[data-size='lg'])style, and cascade to children:ThemeProvideris a no-op in RSCTechnical details:
typeof React.createContext === 'undefined'ThemeProviderandStyleSheetManagerbecome no-ops in RSC (children pass-through)856cf06: feat: update built-in element aliases to include modern HTML and SVG elementsAdded support for modern HTML and SVG elements that were previously missing:
HTML elements:
search- HTML5 search elementslot- Web Components slot elementtemplate- HTML template elementSVG filter elements:
fe*filter primitive elements (feBlend, feColorMatrix, feComponentTransfer, etc.)clipPath,linearGradient,radialGradient- gradient and clipping elementstextPath- SVG text path elementswitch,symbol,use- SVG structural elementsThis 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 propCSS 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 propsaef2ad6: Update shared css property handling tools to latest versions.v6.2.0Compare Source
v6.1.19Compare 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.dcastil/tailwind-merge (tailwind-merge)
v2.6.1Compare Source
Bug Fixes
color-mixnot being detected as color by @dcastil in #591Full Changelog: dcastil/tailwind-merge@v2.6.0...v2.6.1
Thanks to @brandonmcconnell, @manavm1990, @langy, @roboflow, @syntaxfm, @getsentry, @codecov, a private sponsor, @block, @openclaw and more via @thnxdev for sponsoring tailwind-merge! ❤️
v2.6.0Compare Source
New Features
Full Changelog: dcastil/tailwind-merge@v2.5.5...v2.6.0
Thanks to @brandonmcconnell, @manavm1990, @langy, @jamesreaco, @roboflow, @syntaxfm, @getsentry, @codecov, @sourcegraph, a private sponsor and more via @thnxdev for sponsoring tailwind-merge! ❤️
v2.5.5Compare Source
Bug Fixes
Documentation
Full Changelog: dcastil/tailwind-merge@v2.5.4...v2.5.5
Thanks to @brandonmcconnell, @manavm1990, @langy, @jamesreaco, @roboflow, @syntaxfm, @getsentry, @codecov and more via @thnxdev for sponsoring tailwind-merge! ❤️
tailwindlabs/tailwindcss (tailwindcss)
v3.4.19Compare Source
v3.4.18Compare Source
Fixed
supports-[…]queries in arbitrary values (#13605)require.cacheerror when loaded through a TypeScript file in Node 22.18+ (#18665)import.meta.resolve(…)in configs for new enough Node.js versions (#18938)postcss-load-configfor better ESM and TypeScript PostCSS config support with the CLI (#18938)v3.4.17Compare Source
Fixed
v3.4.16Compare Source
Fixed
PluginsConfigallowundefinedvalues (#14668)v3.4.15Compare Source
boxShadowtheme configuration allows arrays (#14856)selection:*variant works in Chrome 131 (#15003)microsoft/TypeScript (typescript)
v5.9.3: TypeScript 5.9.3Compare Source
Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.
For release notes, check out the release announcement
Downloads are available on:
v5.9.2: TypeScript 5.9Compare Source
Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.
For release notes, check out the release announcement
Downloads are available on:
v5.8.3: TypeScript 5.8.3Compare Source
Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.
For release notes, check out the release announcement.
Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), 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.
This PR has been generated by Mend Renovate using a curated preset maintained by