Fix picospinner migration issues, clean up Logger API - #3109
Merged
Conversation
fredrikekelund
commented
Apr 16, 2026
Comment on lines
-63
to
+61
| progressCallback!( message ); | ||
| return; | ||
| } else if ( progressCallback ) { | ||
| progressCallback( message ); |
Contributor
Author
There was a problem hiding this comment.
The non-null assertions on progressCallback were superfluous, so I took this opportunity to remove them.
Collaborator
📊 Performance Test ResultsComparing 16fb816 vs trunk app-size
site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff) |
bcotrim
approved these changes
Apr 16, 2026
bcotrim
left a comment
Contributor
There was a problem hiding this comment.
LGTM and works as expected 👍
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.
Related issues
How AI was used in this PR
Not at all.
Proposed Changes
#3035 migrated from the ora library to picospinner. There are some subtle differences in how these two libraries behave that weren't addressed there, and this PR tackles them.
picospinnerthrows if we call.start()when the spinner is already running. Fix 'Spinner is already running' error when creating sites via CLI #3093 fixed that for thesite createcommand specifically, but this PR generalizes the fix so we can safely call anyLoggermethod without worrying about a crash.Logger.reportSuccessmethod would log a new success line. This behavior disappeared in Replace ora with picospinner #3035, which removed some messages from the logging output. This PR brings back that behavior.Lastly, I removed the
shouldClearSpinnerargument from theLogger.reportSuccessmethod. This was introduced in #1306 to address some CfT feedback on the first version of the CLI, but the better solution is to just not callLogger.reportSuccessat all (which is what we've been doing in most new code we've added since then).Testing Instructions
npm run cli:buildnode apps/cli/dist/cli/main.mjs export --path PATH_TO_SITEand ensure the command completes successfullynode apps/cli/dist/cli/main.mjs preview create --path PATH_TO_SITEand ensure the command completes successfullynode apps/cli/dist/cli/main.mjs site createand ensure the command completes successfullyPre-merge Checklist