Update dependency @linaria/react to ^4.5.4 #92
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/linaria-react-4.x
branch
from
2b6a63a to
459f9dd
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/linaria-react-4.x
branch
from
459f9dd to
120c329
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/linaria-react-4.x
branch
from
120c329 to
70b0525
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/linaria-react-4.x
branch
from
70b0525 to
2024aeb
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/linaria-react-4.x
branch
from
2024aeb to
f291ed3
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/linaria-react-4.x
branch
from
f291ed3 to
aafd150
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/linaria-react-4.x
branch
from
aafd150 to
4e72a71
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/linaria-react-4.x
branch
from
4e72a71 to
58d21d8
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/linaria-react-4.x
branch
from
58d21d8 to
0b55adc
Compare
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.
This PR contains the following updates:
^4.3.2->^4.5.4Release Notes
callstack/linaria (@linaria/react)
v4.5.4Compare Source
Patch Changes
10bcd24: Fix for "The expression evaluated to 'undefined'" in Webpack (fixes #1300 and #1287)10bcd24]v4.5.3Compare Source
Patch Changes
10bcd24]v4.5.2Compare Source
Patch Changes
e59bf80: Shaker mistakenly counts references in types as valuable and keeps referenced variables alive.ae3727f: Fix the issues with processing files that are supposed to be parsed with their respective Babel config.7955724]b191f54]e59bf80]520ba8d]ae3727f]dca076e]v4.5.1Compare Source
Patch Changes
v4.5.0Compare Source
Minor Changes
16c057d: Breaking Change: Performance Optimization forstyledWhen a component is wrapped in
styled, Linaria needs to determine if that component is already a styled component. To accomplish this, the wrapped component is included in the list of variables for evaluation, along with the interpolated values used in styles. The issue arises when a wrapped component, even if it is not styled, brings along a substantial dependency tree. This situation is particularly evident when usingstyledto style components from third-party UI libraries.To address this problem, Linaria will now examine the import location of the component and check if there is an annotation in the
package.jsonfile of the package containing the components. This annotation indicates whether the package includes other Linaria components. If there is no such annotation, Linaria will refrain from evaluating the component.Please note that this Breaking Change solely affects developers of component libraries. In order for users to style components from your library, you must include the
linaria.componentsproperty in the library'spackage.jsonfile. This property should have a mask that covers all imported files with components. Here's an example of how to specify it:Patch Changes
af5bb92: The end of support for Node.js 14. Migration to pnpm 8.16c057d]af5bb92]v4.3.8Compare Source
Patch Changes
54ab61b: Enhance @linaria/shaker strategy: better search in namespace imports, add support for side effect imports, fix file skipping.54ab61b]v4.3.7Compare Source
Patch Changes
1c3f309: Fix tags usage validation (fixes #1224)3402908: Usages ofstyledandcssin Jest no longer trigger the "Using the … tag in runtime is not supported" exception.2e966f2]1c3f309]dbe250b]3402908]v4.3.6Compare Source
Patch Changes
a3ad617: Fix "Invalid usage ofstyledtag" when it's not really invalid. Fixes #1214.a3ad617]v4.3.5Compare Source
Patch Changes
f9df4ed]v4.3.4Compare Source
Patch Changes
28f3f93]71a5b35]61d49a3]v4.3.3Compare Source
Patch Changes
3ce985e]d11174d]Configuration
📅 Schedule: Branch creation - "after 6am" in timezone Asia/Tokyo, 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.