Core: Add try-catch for cross-origin access in Storybook hooks

[ndelangen]

What I did

I noticed chromatic canvas failing due to a parent.[property] access being denied, due to cross origin.

I suspect this is the culpit of the error, so I'm wrapping the code with a try-catch for now.

I do wonder why this is production code, since the comments imply it's only there for internal e2e testing purposes.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

I'll manually check the UI review canvas in chromatic.

This was where I found the error before:
https://www.chromatic.com/component?appId=635781f3500dd2c49e189caf&csfId=manager-sidebar-treenode&specName=Types&buildNumber=24086&k=69499185f7f68d66d9516994-1200px-interactive-true&h=3&b=-1

After this change I can see the canvas corectly, see here:
https://www.chromatic.com/component?appId=635781f3500dd2c49e189caf&csfId=manager-sidebar-treenode&specName=Types&buildNumber=24180&k=69499185f7f68d66d9516994-1200px-interactive-true&h=8&b=-2

So that should no longer happen after this change.

I think we should patch this back, it may also be affecting storybook composition?

If I understand the comment correctly, this code only exists for internal e2e testing purposes.
I suggest we try to find another way to test the behavior without introducing globalThis.parent hooks in the preview runtime code.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 2a10a31

Command	Status	Duration	Result
nx run-many -t compile,check,knip,test,pretty-d...	✅ Succeeded	10m 38s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-12-31 09:48:21 UTC