-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Unable to resolve path to module '@storybook/addon-info' #8324
Comments
I can confirm that the error occurs as of v5.2.2. When version locked to v5.2.1, everything still works as expected. |
I confirm as well with the v5.2.4. Downgrading to the v5.2.1 works as expected as @annaemu suggests. |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
|
Hurrah!! I just released https://github.com/storybookjs/storybook/releases/tag/v5.3.0-alpha.42 containing PR #8764 that references this issue. Upgrade today to try it out! You can find this prerelease on the Closing this issue. Please re-open if you think there's still more to do. |
Whoopee!! I just released https://github.com/storybookjs/storybook/releases/tag/v5.2.6 containing PR #8764 that references this issue. Upgrade today to try it out! |
Describe the bug
We are using storybook ^5.2.1, and have found our builds to be recently failing with
Unable to resolve path to module '@storybook/addon-info'
with no changes. Happens locally and on the build server.We recently upgraded storybook from v4 to v5, which was working before. The branches on the old v4 continue to build. All branches on v5 have started to fail with no changes.
The project does not use Typescript.
To Reproduce
Error happens during the build process when using
import { withInfo } from '@storybook/addon-info';
.The error is also evident in the IDE with eslint, which resolves the path to a directory under AppData, whereas most of the other addons are shown to resolve to a directory under the project.
The
\node_modules\@storybook\addon-info
directory does exist under the project root, but the build process seems to be looking for it somewhere else.System:
Package.json dependencies are as follows:
The text was updated successfully, but these errors were encountered: