[Snyk] Upgrade styled-components from 5.1.1 to 5.3.0#19
Open
[Snyk] Upgrade styled-components from 5.1.1 to 5.3.0#19
Conversation
Snyk has created this PR to upgrade styled-components from 5.1.1 to 5.3.0. See this package in npm: https://www.npmjs.com/package/styled-components See this project in Snyk: https://app.snyk.io/org/alacret/project/2b135843-a909-4db7-ba2f-e7a6d4695d69?utm_source=github&utm_medium=upgrade-pr
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Snyk has created this PR to upgrade styled-components from 5.1.1 to 5.3.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: styled-components
-
5.3.0 - 2021-05-05
-
-
-
5.2.3 - 2021-03-31
-
5.2.2 - 2021-03-30
-
-
-
-
5.2.1 - 2020-10-30
-
5.2.0 - 2020-09-04
-
-
-
-
-
-
-
-
5.2.0-test.12 - 2020-09-02
-
5.2.0-test.11 - 2020-08-31
-
5.2.0-test.10 - 2020-08-30
-
-
-
-
-
-
-
-
-
5.2.0-test.9 - 2020-08-30
-
5.2.0-test.8 - 2020-08-30
-
5.2.0-test.7 - 2020-08-30
-
5.2.0-test.6 - 2020-08-30
-
5.2.0-test.5 - 2020-08-28
-
5.2.0-test.4 - 2020-08-28
-
5.2.0-test.3 - 2020-08-28
-
5.2.0-test.2 - 2020-08-27
-
5.2.0-test.1 - 2020-08-27
-
5.2.0-test.0 - 2020-08-27
-
5.1.1 - 2020-05-25
- Implement
- Added
- Escape every CSS ident character necessary when converting component display names to class names (see #3102) thanks @ kripod!
from styled-components GitHub release notesPass
elementToBeCreatedas a third parameter toshouldForwardPropso 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)
fix an issue with an unguarded window accessor in a SSR path (see #3446)
For React Native based components, pass
testIDdown 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)
Tweak server-side build settings to resolve an issue with jest-dom not being able to pick up generated styles (see #3308) thanks @ Lazyuki
Make sure
StyleSheetManagerrenders 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
keyframesnot receiving a modified stylis instance when using something likestylis-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!
We are planning to release 5.2 on September 2/3, please help us test!
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)
NOTE: This is a behavioral change and might require adjustment in your codebase if you have many
createGlobalStylecomponents in use. We do not think it will affect the majority of projects other than fix existing bugs.createGlobalStyleis nowReact.StrictModecompliantMake sure
StyleSheetManagerrenders 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
keyframesnot receiving a modified stylis instance when using something likestylis-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
Add "engines" to package.json (currently set to Node 10, the oldest supported LTS distribution) (see #3201) thanks @ MichaelDeBoey!
New Functionality
shouldForwardPropAPI for native and primitive platforms, which was previously missing in [v5.1.0] (see #3093)This has been released under a patch bump instead of a minor, since it's only been missing from Native-support.
Bugfixes
useThemehook to named exports for react-primitives entrypoint (see #2982) thanks @ jladuval!Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs