storybook: [Bug]: SB7-beta.36 - Angular: No provider for XXX

Describe the bug

I just upgraded from alpha.33 (which worked alright with Angular v14) to beta.36 (because I upgraded Angular to v15) and now Iā€™m getting a lot of No provider for XXX errors.

E.g. the No provider for HttpClient error does not even go away if I import the HttpClientModule explicitly in a given story, which seems to indicate that something is broken about moduleMetadata decorator (I could be wrong though).

I also tried reverting to beta.34 and beta.33 to no avail.

BUT, after having reverted to beta.27 the problem disappeared and my stories work, so at least I can continue with merging the Angular 15 update branch šŸŽ‰

seems like something along the way broke global Angular providers?

To Reproduce

Sorry, private repository

System

Posting the info output of the version that I reverted to from latest, where my stories work

Environment Info:

  System:
    OS: macOS 13.0.1
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.13.2/bin/yarn
    npm: 8.16.0 - ~/.nvm/versions/node/v16.13.2/bin/npm
  Browsers:
    Chrome: 109.0.5414.119
    Safari: 16.1
  npmPackages:
    @storybook/addon-essentials: 7.0.0-beta.27 => 7.0.0-beta.27
    @storybook/addon-interactions: 7.0.0-beta.27 => 7.0.0-beta.27
    @storybook/angular: 7.0.0-beta.27 => 7.0.0-beta.27
    @storybook/builder-webpack5: 7.0.0-beta.27 => 7.0.0-beta.27
    @storybook/core-server: 7.0.0-beta.27 => 7.0.0-beta.27
    @storybook/eslint-config-storybook: ~3.1.2 => 3.1.2
    @storybook/jest: ~0.0.11-next.0 => 0.0.11-next.0
    @storybook/manager-webpack5: ~7.0.0-alpha.10 => 7.0.0-alpha.10
    @storybook/mdx2-csf: ~1.0.0-next.5 => 1.0.0-next.5
    @storybook/preset-scss: ~1.0.3 => 1.0.3
    @storybook/testing-library: ~0.0.14-next.1 => 0.0.14-next.1
    @storybook/theming: 7.0.0-beta.27 => 7.0.0-beta.27

Additional context

No response

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 17 (8 by maintainers)

Most upvoted comments

@valentinpalkovic I can confirm that worked for me thanks