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.

Sign up for GitHub

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

Jump to bottom

fix: update dependency linaria to v6 #96

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix: update dependency linaria to v6 #96

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 7, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
linaria ^2.0.0 -> ^6.0.0 age adoption passing confidence

Release Notes

callstack/linaria (linaria)

v6.1.0

Compare Source

Minor Changes
Patch Changes
  • 8d4ebd3: chore: bump @​wyw-in-js/* packages

v6.0.0

Compare Source

Major Changes
  • 2ac94b9: BREAKING CHANGE: Linaria has been migrated to wyw-in-js.

Migration Guide

For Users

The main breaking change is that all tooling has been moved from the `@linaria` scope to the `@wyw-in-js` scope. This means that you will need to update your dependencies as follows:

| Old                      | New                       |
| ------------------------ | ------------------------- |
| @​linaria/babel-preset    | @​wyw-in-js/babel-preset   |
| @​linaria/cli             | @​wyw-in-js/cli            |
| @​linaria/esbuild         | @​wyw-in-js/esbuild        |
| @​linaria/rollup          | @​wyw-in-js/rollup         |
| @​linaria/shaker          | discontinued              |
| @​linaria/vite            | @​wyw-in-js/vite           |
| @​linaria/webpack4-loader | discontinued              |
| @​linaria/webpack5-loader | @​wyw-in-js/webpack-loader |

There is no longer a need to install `@linaria/shaker` as it is now part of `@wyw-in-js/transform`, which will be installed automatically with the bundler plugins.

The configuration file has been renamed from `linaria.config.js` (`linariarc`) to `wyw-in-js.config.js` (`.wyw-in-jsrc`).

For Custom Processor Developers

Base classes for processors and most helpers have been moved to `@wyw-in-js/processor-utils`.

All APIs that had `linaria` in their names have been renamed:

-   The field that stores meta information in runtime has been renamed from `__linaria` to `__wyw_meta`
-   The export with all interpolated values has been renamed from `__linariaPreval` to `__wywPreval`
-   The caller name in Babel has been renamed from `linaria` to `wyw-in-js`

For additional information, please visit the [wyw-in-js.dev](https://wyw-in-js.dev).

v5.0.5

Compare Source

Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
  • 88e0761: Rewritten dependecny tree processing with support for wildcard re-exports.
  • cb853e1: All processing stages were merged into one generators-based processor. It allows the implementation of more complex workflows to support features like dynamic imports and re-exports.
Minor Changes
  • 9cb4143: Refactoring of the 1st stage of transformation. It opens the road to processing wildcard reexports.
Patch Changes

v4.5.4

Compare Source

Patch Changes

v4.5.3

Compare Source

Patch Changes

v4.5.2

Compare 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.
  • Updated dependencies [7955724]
  • Updated dependencies [b191f54]
  • Updated dependencies [e59bf80]
  • Updated dependencies [520ba8d]
  • Updated dependencies [ae3727f]
  • Updated dependencies [dca076e]

v4.5.1

Compare Source

Patch Changes

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

v4.1.17

Compare Source

Patch Changes

v4.1.16

Compare Source

Patch Changes

v4.1.15

Compare Source

Patch Changes

v4.1.14

Compare Source

Patch Changes

v4.1.13

Compare Source

Patch Changes

v4.1.12

Compare Source

Patch Changes

v4.1.11

Compare Source

Patch Changes

v4.1.10

Compare Source

Patch Changes

v4.1.9

Compare Source

Patch Changes

v4.1.8

Compare Source

Patch Changes

v4.1.7

Compare Source

Patch Changes

v4.1.6

Compare Source

Patch Changes

v4.1.5

Compare Source

Patch Changes

v4.1.4

Patch Changes

v4.1.3

Patch Changes

v4.1.2

Compare Source

Patch Changes

v4.1.1

Compare Source

Patch Changes

v4.1.0

Compare Source

Patch Changes

v4.0.0

Compare Source

What's Changed

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

  • 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 renovate bot added the maintenance label Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
maintenance
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants