fix(tasty): total css calculation in debug #776
Conversation
🦋 Changeset detectedLatest commit: 822b4b0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📦 NPM canary releaseDeployed canary version 0.0.0-canary-e8aa05f. |
🧪 Storybook is successfully deployed!
|
🏋️ Size limit report
Click here if you want to find out what is changed in this build |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
| rawCSSSize: Math.round(rawData.size * scaleFactor), | ||
| keyframesCSSSize: Math.round(keyframesData.size * scaleFactor), | ||
| propertyCSSSize: Math.round(propertyData.size * scaleFactor), | ||
| }; |
There was a problem hiding this comment.
Bug: Global CSS Extraction Error Causes Division By Zero
A division by zero error can occur when globalTypesTotalSize is 0, but totalGlobalCSSSize is non-zero. This happens if individual global CSS extractions yield no content, but the overall allCSS length implies global CSS exists. The scaleFactor calculation then results in Infinity or NaN, corrupting the adjustedGlobalSizes and debug output.
No description provided.