storybook: [Bug]: Module not found: Error: Can't resolve 'uuid-browser/v4'
Describe the bug
BREAKING CHANGE: The request ‘uuid-browser/v4’ failed to resolve only because it was resolved as fully specified (probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a ‘.mjs’ file, or a '.js’ file where the package.json contains ‘“type”: “module”’). The extension in the request is mandatory for it to be fully specified.
To Reproduce
upgrade storybook to 7.0.2 version
System
Environment Info:
System:
OS: macOS 13.2.1
CPU: (8) arm64 Apple M1 Pro
Binaries:
Node: 18.13.0 - ~/.nvm/versions/node/v18.13.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v18.13.0/bin/yarn
npm: 8.19.3 - ~/.nvm/versions/node/v18.13.0/bin/npm
Browsers:
Chrome: 111.0.5563.146
Safari: 16.3
npmPackages:
@storybook/addon-actions: ^7.0.2 => 7.0.2
@storybook/addon-essentials: ^7.0.2 => 7.0.2
@storybook/addon-interactions: ^7.0.2 => 7.0.2
@storybook/addon-links: ^7.0.2 => 7.0.2
@storybook/addon-mdx-gfm: ^7.0.2 => 7.0.2
@storybook/cli: ^7.0.2 => 7.0.2
@storybook/react: ^7.0.2 => 7.0.2
@storybook/react-webpack5: ^7.0.0 => 7.0.2
@storybook/testing-library: ^0.1.0 => 0.1.0
Additional context
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 26
- Comments: 23 (6 by maintainers)
Commits related to this issue
- Fix #21916 - using uuid library instead of uuid-browser The library uuid-browser doesn't support esm, so the start with webpack fails. — committed to misino/storybook by deleted user a year ago
- Fix #21916 - using uuid library instead of uuid-browser The library uuid-browser doesn't support esm, so the start with webpack fails. — committed to misino/storybook by deleted user a year ago
- Upgrade to Storybook v7 (#5780) **User-Facing Changes** None **Description** Depends on #5776 Resolves FG-2861 Includes a temporary patch to work around https://github.com/storybookjs/storyb... — committed to foxglove/studio by jtbandes a year ago
I hope they’ll give it high priority and release a patch soon.
@shilman can you please have a look at this and the corresponding PR https://github.com/storybookjs/storybook/pull/22037 so this can get approved and solved ?
This issue is still happening on version 7.0.5 and probably blocking a lot of people.
Son of a gun!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.0.7 containing PR #22037 that references this issue. Upgrade today to the
@latest
NPM tag to try it out!@KaiHotz if i merge the PR and publish a prerelease would you be able to test it?
@KaiHotz thanks for letting me know! Will release the patch to 7.0.x today
Crikey!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.1.0-alpha.8 containing PR #22037 that references this issue. Upgrade today to the
@future
NPM tag to try it out!@shilman thank your for the quick response, i also can confirm that the issue is resolved on v7.0.7 @misino thank you for the PR and fixing this issue
Hello,
I think, we just need to wait this pull request to be approved: https://github.com/storybookjs/storybook/pull/22037. this pull will fix the issue
I hope so.
any update to fix this issue? i have the same problem when i add the addon “@storybook/addon-actions”
issue happens also in “@storybook/addon-actions”: “^7.0.4”
FYI