You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to latest Chrome update, sometimes I get the Ad Removed error for the storybook build for a different project. How are you guys managing to optimize the bundle size when the bundle built by webpack config is huge.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When I run

npm run build-storybook
, I get a warning stating the asset size exceeds the recommended limit. Please refer to the following screenshot:But, when I access the published storybook URL (for example: https://angular.carbondesignsystem.com/iframe.html?args=align:end;size:lg&id=components-accordion--basic&viewMode=story), the network calls made do not show the same bundle size. (see the following screenshot)

Due to latest Chrome update, sometimes I get the Ad Removed error for the storybook build for a different project. How are you guys managing to optimize the bundle size when the bundle built by webpack config is huge.
Beta Was this translation helpful? Give feedback.
All reactions