Core: Pass proper stack of an error

[extempl]

Reopening #14336

Issue: Stack of an error is not the error's, but the storybook's.

What I did

Pass stack explicitly (toString does not include it).

How to test

• Is this testable with Jest or Chromatic screenshots? - Passively?
• Does this need a new example in the kitchen sink apps? - No
• Does this need an update to the documentation? - No

If your answer is yes to any of these, please make sure to include it in your PR.

[MichaelArestad]

This looks identical to the previous PR you made, #14336. Can you provide an example or detailed steps to reproduce the issue you are having?

[extempl]

@MichaelArestad @yannbf indeed it is identical, this is the only way I can 'reopen' it, since it was closed.
The example of the issue and solution is in the latest comment: #14336 (comment)

The issue is that (new Error).toString does not contain a stacktrace, but message only. The stack trace is visible after that does not help to solve any problems occured because of the error, as it shows nothing, but the fact that something went wrong and the error message.
You can see that in example when you attaching e.stack - it shows the method where the original error occured, not where it was re-thrown.
So I need to have an actual stack trace, and not the storybook-logger which is only shows where the exception was re-thrown.
Also my fix is backwards compatible, I do not really see the reason to not merge it.

[yannbf]

Thanks for this PR @extempl! It certainly makes things much better. I simulated this error by calling a function that does not exist in a .stories file.

Here's the result prior to your fix:

Here's with your fix:

Great contribution! 👏

[shilman]

@yannbf any chance you can help get CI to pass?

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit 9993215. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx run-many --target=prepare --all --parallel --max-parallel=15

---

Sent with 💌 from NxCloud.

[yannbf]

@shilman this seems good to go!