chore: Script the generate of Verdaccio's database to skip slow publish - #10455
Open
snowystinger wants to merge 10 commits into
Open
chore: Script the generate of Verdaccio's database to skip slow publish#10455snowystinger wants to merge 10 commits into
snowystinger wants to merge 10 commits into
Conversation
|
Build successful! 🎉 |
Agent Skills ChangesModified (2)
InstallReact Spectrum S2: React Aria: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes
getting our packages published to verdaccio was taking >5min, our longest running CI job. This was slow because we were starting up verdaccio, then publishing everything to it. I'm unsure exactly why that was sooo slow, but they haven't fixed it in the newer versions of verdaccio. It's predictable what the verdaccio database storage looks like though, so it's not that hard for an AI agent to script this. So that's what I've done. It's cut the run time of the CI job by about >50%, taking 2 min 30s.
We could push this further by sidestepping the yarn versioning step as well since that queries npm to see current versions, but theoretically we already know our version as it's stored in our package.json.
You can test that this verdaccio build isn't pulling from the latest on npm but rather the state of this branch by looking at ColorField in the test apps vs before the commit for handling the "Enter" key on main. On main, Enter does nothing, in this branch, it will commit the value, just like a NumberField.
✅ Pull Request Checklist:
📝 Test Instructions:
🧢 Your Project: