Skip to content
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

[Bug]: Uncaught TypeError: __webpack_require__.nmd is not a function #27354

Closed
yutao815 opened this issue May 24, 2024 · 7 comments · Fixed by #27361
Closed

[Bug]: Uncaught TypeError: __webpack_require__.nmd is not a function #27354

yutao815 opened this issue May 24, 2024 · 7 comments · Fixed by #27361

Comments

@yutao815
Copy link

Describe the bug

I update angular to v18,then get a error:Uncaught TypeError: webpack_require.nmd is not a function.

Reproduction link

sorry

Reproduction steps

No response

System

Storybook Environment Info:

  System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
  Binaries:
    Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
    npm: 9.1.2 - D:\Program Files\nodejs\node_global\npm.CMD <----- active
  Browsers:
    Chrome: 124.0.6367.208
    Edge: Chromium (123.0.2420.97)
  npmPackages:
    @storybook/addon-docs: ^8.1.3 => 8.1.3
    @storybook/addon-essentials: ^8.1.3 => 8.1.3
    @storybook/addon-interactions: ^8.1.3 => 8.1.3
    @storybook/addon-links: ^8.1.3 => 8.1.3
    @storybook/addon-themes: ^8.1.3 => 8.1.3
    @storybook/angular: ^8.1.3 => 8.1.3
    @storybook/blocks: ^8.1.3 => 8.1.3
    @storybook/test: ^8.1.3 => 8.1.3
    eslint-plugin-storybook: ^0.8.0 => 0.8.0
    storybook: ^8.1.3 => 8.1.3

Additional context

No response

@playerx
Copy link

playerx commented May 24, 2024

Experiencing the same issue with storybook v8+.

And because of that, HMR & component remounting doesn't work. I need to refresh page manually to see the updated style/props on the component.

@playerx
Copy link

playerx commented May 24, 2024

Unfortunatelly I can't rollback to v7, because I use input signals and it's supported in the latest versions of storybook.

@playerx
Copy link

playerx commented May 24, 2024

Good news:
I've checked all recent versions and it seems there is a regress in v8.1.1 -> v8.1.2

With v8.1.1 it works properly. with v8.1.2 and v8.1.3 there is an error mentioned in this post, on load.

There is an error for Angular 17 as well if @storybook/angular library version is v8.1.2 or v8.1.3

@playerx
Copy link

playerx commented May 24, 2024

@playerx
Copy link

playerx commented May 24, 2024

Created a minimal repo which can reproduce the issue:
https://github.com/playerx/storybook-angular-issue/tree/main

Using @storybook/angular - v8.1.2 & angular - v17

@valentinpalkovic
Copy link
Contributor

Does the following canary release fix your issue?

npx [email protected] upgrade

@playerx
Copy link

playerx commented May 25, 2024

@valentinpalkovic Yes! checked and in the following canary release, the issue is fixed 👌🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants