Update dependency @linaria/core to v4.5.4 - abandoned

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@linaria/core	4.2.8 -> 4.5.4

---

Release Notes

callstack/linaria (@​linaria/core)

v4.5.4

Compare Source

Patch Changes

• Updated dependencies [10bcd24]
  • @​linaria/utils@​4.5.3
  • @​linaria/core@​4.5.4
  • @​linaria/react@​4.5.4
  • @​linaria/tags@​4.5.4

v4.5.3

Compare Source

Patch Changes

• 7955724: Nothing has changed. Just moved some utils and types from babel to utils package.
• e59bf80: Shaker mistakenly counts references in types as valuable and keeps referenced variables alive.
• Updated dependencies [7955724]
• Updated dependencies [b191f54]
• Updated dependencies [e59bf80]
• Updated dependencies [520ba8d]
• Updated dependencies [ae3727f]
• Updated dependencies [dca076e]
  • @​linaria/core@​4.5.3
  • @​linaria/react@​4.5.3
  • @​linaria/tags@​4.5.3
  • @​linaria/utils@​4.5.2

v4.5.2

Compare Source

Patch Changes

• Updated dependencies [85e74df]
• Updated dependencies [1bf5c5b]
  • @​linaria/utils@​4.5.1
  • @​linaria/tags@​4.5.2

v4.5.1

Compare Source

Patch Changes

• ceca161: Enable optimisation from #​1276 for complex expressions such as styled(Component as unknow) or styled(connect(Component)).

• 1325830: Variables in props-based interpolation functions are no longer required for the evaluation stage.
  Here's an example:

  import { getColor } from "very-big-library";
  
  export const Box = styled.div\`
    color: ${props => getColor(props.kind)};
  \`;
  

  In versions prior to and including 4.5.0, the evaluator would attempt to import getColor from very-big-library, despite it having no relevance to style generation. However, in versions greater than 4.5.0, very-big-library will be ignored.

• Updated dependencies [ceca161]

• Updated dependencies [1325830]

  • @​linaria/tags@​4.5.1
  • @​linaria/core@​4.5.1

v4.5.0

Compare Source

Minor Changes

• 16c057d: Breaking Change: Performance Optimization for styled

  When 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 using styled to 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.json file 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.components property in the library's package.json file. This property should have a mask that covers all imported files with components. Here's an example of how to specify it:

  "linaria": {
    "components": "**/*"
  }

Patch Changes

• 00b43a6: Cannot find module 'xxx' with esbuild 0.17 and linaria 4.2
• af5bb92: The end of support for Node.js 14. Migration to pnpm 8.
• Updated dependencies [890b4ac]
• Updated dependencies [418e40a]
• Updated dependencies [05ad266]
• Updated dependencies [16c057d]
• Updated dependencies [af5bb92]
  • @​linaria/utils@​4.5.0
  • @​linaria/babel-preset@​4.5.0

v4.2.10

Compare Source

Patch Changes

• Updated dependencies [54ab61b]
  • @​linaria/tags@​4.3.5
  • @​linaria/utils@​4.3.4

v4.2.9

Compare Source

Patch Changes

• Updated dependencies [f9df4ed]
  • @​linaria/utils@​4.3.2

---

Configuration

📅 Schedule: Branch creation - "monthly" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.