Bot releases are visible (Hide)
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
features
for fine-tuning the build and evaluation process.+exp
in interpolations.type
annotation may lead to an unexpected increase in the evaluated codebase.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": "**/*"
}
void
-expression causes too aggressive tree-shaking. Fixes #1055.variableNameSlug
option that allows to customize css variable names (closes #1053).bc0cbeea: A completely new async mode with native support for Vite, Rollup, esbuild and Webpack resolvers.
BREAKING CHANGES: Despite the fact, that it should be fully compatible with 3.0 and 2.0 branches, the new version of styles evaluator can have some serious bugs which can make your project unbuildable (however, since there is no runtime, if the build is finished successfully, everything will continue work as it was on 2.0 and 3.0). If you face some problems please let us know and we will fix it as soon as possible.
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago