Core: Don't log a console error when the story is missing

[tmeasday]

It doesn't really add anything and it trips up tools like storyshots.

@yannbf I wasn't actually able to reproduce this problem in Storyshots in any of the internal projects however.

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit 89c38f7. 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]

Interesting. I see it in the feat/sb-6.4 branch of this project https://github.com/yannbf/mealdrop/blob/77e45fc998e63e5d7d526d0369842a5d4e61c64f/src/storybook-snapshot.test.ts#L5

There must be something wrong I'm doing there

[tmeasday]

I'm happy to merge this anyway, but I'll see if I can figure out what's happening here.

[tmeasday]

It's weird, the code (that should log the error) runs in our monorepo tests, it just seems like console.error() is getting swallowed somewhere (as is console.warn(), but console.log() isn't -- any idea why @ndelangen? This is in the monorepo's storyshots tests).

I'm not going to dig deeper into jest configuration here, I say we just merge this @yannbf

[yannbf]

It's weird, the code (that should log the error) runs in our monorepo tests, it just seems like console.error() is getting swallowed somewhere (as is console.warn(), but console.log() isn't -- any idea why @ndelangen? This is in the monorepo's storyshots tests).

I'm not going to dig deeper into jest configuration here, I say we just merge this @yannbf

Sounds good! We can merge and investigate later. It's a simple change anyway!