chore: Update WebSocket content reload logger prefix for clarity #3522
Conversation
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
commit: |
farnabaz
approved these changes
Sep 5, 2025
Member
farnabaz
left a comment
farnabaz
left a comment
There was a problem hiding this comment.
Oh I've missed the base branch in your PR. Thanks for creating new one
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updated the console log prefix from "[Content]" to "[Nuxt Content: Hot Content Reload]"
to make it clear that the messages refer to hot-reloading of Nuxt Content.
My previous PR (#3515) was merged into the v3 branch instead of main.
🔗 Linked issue
❓ Type of change
📚 Description
📝 Checklist