fix(logger): use source maps for error stack traces in browser pretty logger

[luchersou]

Closes #6090

Problem

The prettyLoggerBrowser was passing the error as a string to console.error via Cause.pretty(...), which causes the browser to lose the reference to the original Error object and therefore can't resolve source maps.

Solution

Pass the actual Error objects alongside the formatted string using Cause.prettyErrors(cause), so the browser DevTools can resolve source maps correctly.

Before

After

Note

The current output shows both the formatted string from Cause.pretty and the _PrettyError objects, which results in the stack trace appearing twice.

I'm open to feedback on the preferred approach:

1. Keep both (current fix) — preserves Effect's pretty formatting + source maps
2. Pass only the Error objects — cleaner output, similar to the workaround shown in the issue

Happy to adjust based on maintainer preference!

[changeset-bot]

⚠️ No Changeset found

Latest commit: c69da0a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR