linaria

Patch Changes

• Updated dependencies [ceca1611]
• Updated dependencies [13258306]
  • @linaria/[email protected]

Patch Changes

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

• 13258306: 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.

Patch Changes

• Updated dependencies [ceca1611]
• Updated dependencies [13258306]
  • @linaria/[email protected]

Patch Changes

• Updated dependencies [ceca1611]
• Updated dependencies [13258306]
  • @linaria/[email protected]
  • @linaria/[email protected]

Patch Changes

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

• 13258306: 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 [ceca1611]

• Updated dependencies [13258306]

  • @linaria/[email protected]
  • @linaria/[email protected]

Patch Changes

• Updated dependencies [ceca1611]
• Updated dependencies [13258306]
  • @linaria/[email protected]
  • @linaria/[email protected]
  • @linaria/[email protected]
  • @linaria/[email protected]
  • @linaria/[email protected]
  • @linaria/[email protected]

Patch Changes

• Updated dependencies [ceca1611]
• Updated dependencies [13258306]
  • @linaria/[email protected]

Patch Changes

• Updated dependencies [ceca1611]
• Updated dependencies [13258306]
  • @linaria/[email protected]

Patch Changes

• Updated dependencies [ceca1611]
• Updated dependencies [13258306]
  • @linaria/[email protected]

Patch Changes

• Updated dependencies [ceca1611]
• Updated dependencies [13258306]
  • @linaria/[email protected]

Patch Changes

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

• 13258306: 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 [ceca1611]

• Updated dependencies [13258306]

  • @linaria/[email protected]
  • @linaria/[email protected]

Patch Changes

• Updated dependencies [ceca1611]
• Updated dependencies [13258306]
  • @linaria/[email protected]
  • @linaria/[email protected]
  • @linaria/[email protected]

Minor Changes

• 16c057df: 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

• af5bb92d: The end of support for Node.js 14. Migration to pnpm 8.
• Updated dependencies [418e40af]
• Updated dependencies [16c057df]
• Updated dependencies [af5bb92d]
  • @linaria/[email protected]
  • @linaria/[email protected]

Minor Changes

• 16c057df: 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

• af5bb92d: The end of support for Node.js 14. Migration to pnpm 8.
• Updated dependencies [418e40af]
• Updated dependencies [16c057df]
• Updated dependencies [af5bb92d]
  • @linaria/[email protected]
  • @linaria/[email protected]

Minor Changes

• 16c057df: 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

• af5bb92d: The end of support for Node.js 14. Migration to pnpm 8.
• Updated dependencies [16c057df]
• Updated dependencies [af5bb92d]
  • @linaria/[email protected]
  • @linaria/[email protected]

Minor Changes

• 16c057df: 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

• af5bb92d: The end of support for Node.js 14. Migration to pnpm 8.
• a6a29da7: Fix vite css url() resolve error
• Updated dependencies [890b4aca]
• Updated dependencies [418e40af]
• Updated dependencies [05ad266c]
• Updated dependencies [16c057df]
• Updated dependencies [af5bb92d]
  • @linaria/[email protected]
  • @linaria/[email protected]
  • @linaria/[email protected]

Minor Changes

• 16c057df: 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

• 890b4aca: Sometimes Babel doesn't mark removed nodes as removed. An additional check was added. Fixes #1262
• 05ad266c: Improved compatibility with redux and some other libraries.
• af5bb92d: The end of support for Node.js 14. Migration to pnpm 8.
• Updated dependencies [16c057df]
• Updated dependencies [af5bb92d]
  • @linaria/[email protected]

Minor Changes

• 16c057df: 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

• af5bb92d: The end of support for Node.js 14. Migration to pnpm 8.
• Updated dependencies [890b4aca]
• Updated dependencies [05ad266c]
• Updated dependencies [16c057df]
• Updated dependencies [af5bb92d]
  • @linaria/[email protected]
  • @linaria/[email protected]

Patch Changes

• af5bb92d: The end of support for Node.js 14. Migration to pnpm 8.
• Updated dependencies [16c057df]
• Updated dependencies [af5bb92d]
  • @linaria/[email protected]

Patch Changes

• af5bb92d: The end of support for Node.js 14. Migration to pnpm 8.
• Updated dependencies [890b4aca]
• Updated dependencies [418e40af]
• Updated dependencies [05ad266c]
• Updated dependencies [16c057df]
• Updated dependencies [af5bb92d]
  • @linaria/[email protected]
  • @linaria/[email protected]