feat: show stack-trace of unhandled errors with DEBUG env

[tobiasdiez]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 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)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

If an unhandled error occurs somewhere, nito only prints the error message. This makes it hard to locate where the error occurs and how to fix it. With this PR, the full stacktrace is printed for an error.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

Hi @tobiasdiez, and thanks for this PR. But normally, all Promise errors should be handled. These handles are just a fallback to ensure Node.js doesn't exit the process.

We might support showing full stacks on fallback behind an environment variable flag like proces.env.DEBUG.

But I would also like to know your usage that ends with unhandled flags.

[tobiasdiez]

Very early in the migration to nuxt3, I've encountered an error that was only printed through these "unhandled" error handlers. I sadly don't remember the exact context, but I added the the detailed error reporting in JabRef/JabRefOnline@20fac0a, so maybe something related to the runtime config.

If I encounter this again, I'll let you know where/why it occurred.