Storybook not recovering from errors "Error: _get__(...).unmountComponentAtNode is not a function"

[wallslide]

If an error occurs in a story, after fixing the error the story is stuck in an error state.

I'm using version 1.34.0

Expected:
The story will 'recover' and return to a working state after the coding/syntax error is fixed.

Actual:
The following error replaces the original error:

Error: _get__(...).unmountComponentAtNode is not a function

Refreshing the browser fixes the problem until the next time a coding/syntax error occurs.

[arunoda]

Is it possible to get a kind of a sample project. So, I can work on this.

[arunoda]

May be related to this: #276

[PEM--]

Got this issue too since 1.34.x. I need to it a full reload each time the red warning is displayed.

[arunoda]

Yep. Found the issue and fixed with the newest version: v1.35.1

[PEM--]

Thanks 👍 You nailed it.

[arunoda]

Great. Going to close this then :)

[markerikson]

@arunoda : Can you clarify what exactly the issue was? I'm seeing the same issue in my own app, and this is the only real hit for the specific error message.

[arunoda]

@markerikson are you using the latest version of Storybook?
If that's the latest, could you open a new issue with a way to reproduce the issue.

[markerikson]

Ah... no, I'm not using Storybook at all, I'm just using redbox-react in my own application, and seeing this same error message. Was curious exactly what you did to work around things.

[arunoda]

Actually, not we are using a our own error box. We don't use react-redbox anymore.