New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Addon-controls: esm is not defined
error
#15773
Comments
We are facing the same issue from some of our stories when navigate through controls. |
@khylerlin which version are you using, and do you happen to know which version the issue started to appear in? |
@shilman We are now using 6.4.0-alpha.20, and not sure what version started to appear this issue. I encountered this issue almost the issue has been created on Aug 6. |
This issue occurs on a variety of alpha builds. Moreover, it works fine when running Storybook locally via |
Additionally, #15710 is correct in the explanation of behavior but the proposed downgrade does not work. Load the page, navigate to a component that works, click the actions tab, navigate to a component that previously failed and the component is rendered. However, some additional deprecation warnings are emitted. Interestingly, the components which appear to cause the failure also have Angular |
esm is not defined
error
I found the guilty commits, investigation in progress in #15812. |
Same here, we're facing the same issue (except on local server). storybook: 6.3.6
storybook/builder-webpack5: 6.4.0-alpha.1
angular: 12.1.0
node: 14.17.4
npm: 6.14.14 |
Works for me till v6.4.0-alpha.16
|
Egads!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.4.0-alpha.30 containing PR #15812 that references this issue. Upgrade today to the
Closing this issue. Please re-open if you think there's still more to do. |
Describe the bug
Site breaks when navigating to https://next--storybookjs.netlify.app/angular-cli/?path=/story/addons-controls--basic
Check the Console
vendors~main.329f7787c62cee5c3a74.manager.bundle.js:2 ReferenceError: esm is not defined
The text was updated successfully, but these errors were encountered: