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.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: optimize memory usage when building storybook by using swc #22975

Merged
merged 2 commits into from
Feb 15, 2024

Conversation

davidmurdoch
Copy link
Contributor

@davidmurdoch davidmurdoch commented Feb 15, 2024

Building storybook in CI seems to fail often -- probably due to running out of memory. Changing the compiler to swc might help (according to storybookjs/storybook#6408 (comment)).

I don't know what the ramifications of this change may be (I don't even know what storybook is for 馃槄). So someone with knowledge here should review this PR.

Copy link
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@github-actions github-actions bot locked and limited conversation to collaborators Feb 15, 2024
@HowardBraham HowardBraham reopened this Feb 15, 2024
@metamaskbot
Copy link
Collaborator

Builds ready [efa54b4]
Page Load Metrics (1971 卤 233 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint2235803577938
domContentLoaded30234844723
load22425731971485233
domInteractive30234844723
Bundle size diffs
  • background: 0 Bytes (0.00%)
  • ui: 0 Bytes (0.00%)
  • common: 0 Bytes (0.00%)

@@ -45,7 +45,7 @@ const LogoItem = ({ Component }) => {
backgroundColor={BackgroundColor.backgroundDefault}
>
<Box marginBottom={2}>{Component}</Box>
<Text>{`${Component.type.__docgenInfo.displayName}`}</Text>
<Text>{`${Component.type.name}`}</Text>
</Card>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this just deprecated? Don't see any visual changes

Screenshot 2024-02-16 at 8 49 22鈥疉M Screenshot 2024-02-16 at 8 49 02鈥疉M

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not completely sure, but once @davidmurdoch turned on useSWC, this stopped working without changing Component.type.__docgenInfo.displayName to Component.type.name.

Copy link
Contributor

@georgewrmarshall georgewrmarshall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for these fixes 馃檹

@davidmurdoch davidmurdoch changed the title test: try to optimize memory usage in storybook by using swc test: optimize memory usage when building storybook by using swc Feb 15, 2024
@davidmurdoch davidmurdoch marked this pull request as ready for review February 15, 2024 19:53
@davidmurdoch davidmurdoch requested a review from a team as a code owner February 15, 2024 19:53
@HowardBraham HowardBraham merged commit c6cb88e into develop Feb 15, 2024
65 of 66 checks passed
@HowardBraham HowardBraham deleted the fix-storybook-mem-issue branch February 15, 2024 20:09
@metamaskbot metamaskbot added the release-11.12.0 Issue or pull request that will be included in release 11.12.0 label Feb 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
release-11.12.0 Issue or pull request that will be included in release 11.12.0 team-extension-platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants