-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Add script for copying build output to package dist
directories
#3540
Conversation
@mcansh Any clue why we'd suddenly be running out of memory in CI? I don't feel like anything has substantially changed about the build other than including the Rollup TS plugin, and I have no such issues w/ Node's default memory limit running locally. |
nothing's jumping out at me, but i can take a look |
the new build does use almost 3GB of memory though, where as the old one used less than 1GB, so it might be related however according to https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources they should have 7GB of memory, but im not sure how much of that is actually usable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Builds looked ok to me locally. Think it's worth publishing an experimental from here and actually npm installing a few things to make sure it all looks good?
@brophdawg11 Successfully tested with |
🤖 Hello there, We just published version Thanks! |
This will be useful for publishing via Changesets. We can remove this once we've reconfigured Rollup accordingly.