Error: received updateGlobals but was unable to determine the source of the event, received updateGlobals but was unable to determine the source of the event
See original GitHub issueDescribe the bug When I try to build and serve the build version of storybook this issue arises.
To Reproduce Run
build-storybook -c .storybook -o .storybook-static
npx serve -s .storybook-static
System Mac OS Dependencies:
"react": "^16.13.1",
"@storybook/addon-actions": "^6.1.20",
"@storybook/addon-essentials": "^6.1.20",
"@storybook/addon-knobs": "^6.1.20",
"@storybook/addon-links": "^6.1.20",
"@storybook/node-logger": "^6.1.20",
"@storybook/preset-create-react-app": "^3.1.6",
"@storybook/react": "^6.2.9"
Below is my .storybook/main.js
file
module.exports = {
stories: ['../src/**/*.stories.mdx', '../src/**/*.stories.@(js|jsx|ts|tsx)'],
addons: [
'@storybook/addon-links',
'@storybook/addon-essentials',
'@storybook/preset-create-react-app',
],
};
Additional context Throws the following errors in the console,
- received sharedStateChanged-manager-storybook/viewport but was unable to determine the source of the event
- received updateGlobals but was unable to determine the source of the event
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (1 by maintainers)
Top Results From Across the Web
manager received updateGlobals but was unable ... - Issuehunt
Error: manager received updateGlobals but was unable to determine the source of the event #15658 ; Describe the bug When I try to...
Read more >Broken build with updated Storybook (5.3) Configuration
js, manager.js, and preview.js. When I publish with npm this is the error I see this, even though the build does not fail:....
Read more >Storybook throwing errors - Stack Overflow
The error log is pointing out that your min-indent package may be missing from your node_modules folder for whatever reason.
Read more >3 Manual closing of problems - Zabbix
2 Other event sources ... 8 Templates and template groups ... there may be cases when it is difficult to determine if a...
Read more >GWT Release Notes
Uncaught exception handler will now receive all errors on the page, ... third-party libraries to handle events that GWT itself doesn't know about...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
FYI I am getting this error when using this recipe: https://github.com/storybookjs/storybook/blob/next/addons/docs/docs/recipes.md#reordering-docs-tab-first
Both when running storybook locally and with the static build. I would love to have a way to reorder the tabs without causing this warnings.
Seems this still exists!