🔗 Linked issue

resolves #25260
resolves #13470

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR adds a new feature (can be disabled by setting features.devLogs to false) which records all console events on the server (nitro runtime + vue runtime). It bundles up logs to the next request, and then continues to stream them to the client. Any logs that don't happen on the client are displayed in the console.

A hook (which I envision being consumed by devtools - cc: @antfu) is called whenever new logs are available.

You can currently set features.devLogs to silent to disable them being output to the browser console while still being able to consume them in devtools, or elsewhere. I'm wondering if it makes sense for this to be the default, so things are less 'noisy'... (Thoughts very much welcome!)

Here's a demo of logs being consumed by a custom hook + vue-sonner:

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.