fix: don't define error.message if it's not configurable

[paoloricciuti]

Closes #16146

For the moment I changed this to not include the rest of the logs at all but i wonder if we should at least console.error them even if we don't change the original message (or if it could make sense to throw a different error, but that could be tricky).

Ok I've also added a console.error with the updated info, with an initial line that tells the user that it's not a second error, just a second console.error

WDYT?

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• Prefix your PR title with feat:, fix:, chore:, or docs:.
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.
• If this PR changes code within packages/svelte/src, add a changeset (npx changeset).

Tests and linting

• Run the tests with pnpm test and lint the project with pnpm lint

[changeset-bot]

🦋 Changeset detected

Latest commit: 53afa99

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
svelte	Patch

Not sure what this means? Click here to learn what changesets are.

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

[github-actions]

Playground

pnpm add https://pkg.pr.new/svelte@16149

[dummdidumm]

This is ... a lot 😄 I would trim this down to just this, or just not log anything at all. I don't know how many people will have worse stacks as a result, but I doubt it's many

Suggested change

	console.error(
	"The following it's not a separate error: we usually modify the error message to show you this information but `message` was non configurable so we print them in a separate log.\n" +
	error.message +
	`\n${component_stack}\n`
	);
	console.error(
	"[adjusted stack] " +
	error.message +
	`\n${component_stack}\n`
	);

[paoloricciuti]

Yeah I feared it would've been a lot but also wanted to make it clear it was not a separate error

[Rich-Harris]

this seems like a real edge case. i would just skip the console.error personally

[paoloricciuti]

this seems like a real edge case. i would just skip the console.error personally

Yeah it's also fine...let me revert it