Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade styled-components to version 5.3.10 #1099

Closed

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Apr 24, 2023

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ styled-components (5.1.1 → 5.3.10) · Repo · Changelog

Release Notes

5.3.10

What's Changed

  • fix: Do not add px to unitless CSS variables by @Lazyuki in #3975

Full Changelog: v5.3.9...v5.3.10

5.3.9

What's Changed

  • [v5] Make styled components work when the Object prototype is frozen by @jportner in #3964

Full Changelog: v5.3.8...v5.3.9

5.3.8

What's Changed

fix(constants): rework process env guard

Full Changelog: v5.3.7-fixed...v5.3.8

5.3.6

What's Changed

New Contributors

Full Changelog: v5.3.5...v5.3.6

5.3.5

Add statement of solidarity against the war on Ukraine 🇺🇦

5.3.3

What's Changed

New Contributors

Full Changelog: v5.3.1...v5.3.3

5.3.1

  • Fix forced server-side mode not triggering global styles (See #3566)

  • Fix SSR collisions caused by insufficient hash inputs and reordering of groups on the client, which is a regression in v5.2.0 (See #3563)

  • Fix dynamic creation React warning for React v18, backported to v5 by @lynndylanhurley (See #3564)

  • Add missing typeof window check when checking for duplicate instances of styled-components (See #3553)

  • Prevent ServerStyleSheet from emitting empty style tags, which would cause issues in IE11 (See #3555)

  • Support css tagged templates inside style objects, by @roginfarrer and @dvingo (See #3469)

5.3.0

  • Pass elementToBeCreated as a third parameter to shouldForwardProp so that the user-specified function can decide whether to pass through props based on whether the created element will be a tag or another component. (see #3436)

  • Fix React Native components accepts function as style prop. (see #3389)

5.2.3

fix an issue with an unguarded window accessor in a SSR path (see #3446)

5.2.2

  • For React Native based components, pass testID down to the native component if specified for an easier time testing. (see #3365)

  • Enable users of the babel macro to customize the styled-components import with importModuleName (see #3422)

  • [fix] COMPLEX_SELECTOR_PREFIX.includes wasn't transpiled (see #3397)

5.2.1

Tweak server-side build settings to resolve an issue with jest-dom not being able to pick up generated styles (see #3308) thanks @Lazyuki

5.2.0

  • Make sure StyleSheetManager renders all styles in iframe / child windows (see #3159) thanks @eramdam!

  • Rework how components self-reference in extension scenarios (see #3236); should fix a bunch of subtle bugs around patterns like & + &

  • Fix keyframes not receiving a modified stylis instance when using something like stylis-plugin-rtl (see #3239)

  • Big performance gain for components using style objects (see #3239)

  • We no longer emit dynamic classNames for empty rulesets, so some className churn may occur in snapshots

  • Preallocate global style placement to ensure cGS is consistently inserted at the top of the stylesheet; note that this is done in runtime order so, if you have multiple cGS that have overlapping styles, ensure they're defined in code in the sequence you would want them injected (see #3239)

  • Add "engines" to package.json (currently set to Node 10, the oldest supported LTS distribution) (see #3201) thanks @MichaelDeBoey!

Finally, special thanks to @willheslam for testing and some last minute fixes on this release!

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu
Copy link
Contributor Author

depfu bot commented May 27, 2023

Closed in favor of #1116.

@depfu depfu bot closed this May 27, 2023
@depfu depfu bot deleted the depfu/update/develop/npm/styled-components-5.3.10 branch May 27, 2023 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant