Cannot find module '@redwoodjs/testing/web' when running Storybook

Having followed the tutorial up to chapter 5, i am getting this error in the dev console when i run yarn rw storybook:

All of the stories just render a blank page in the UI, the Cells and Pages are not even listed.

I am unsure whether this is typescript related or not – from my experience any typescript errors are gracefully handled when compiling to JS, and this seems to be a webpack error message.

However, when i run the js-based https://github.com/redwoodjs/redwood-tutorial there is no such error – the dependencies listed in package.json are identical to my project, which you can check out here: https://github.com/Philzen/redwoodblog-tutorial-typescript

Any ideas what’s going on here greatly appreciated.

[dac09]

OK FOUND ISSUE! This solves both issues.

Tried a bunch of theories, but pulling on the thread from this issue, it looks like this happens when storybook for some reason picks webpack 4 accidentally (extrapolating from this thread) - When there are multiple versions of webpack 5 (in our case, redwood is using 5.70.0, but storybook wants 5.71.0) - see this output from yarn why

gitpod /workspace/redwoodblog-tutorial-typescript (main) $ yarn why webpack
├─ @redwoodjs/core@npm:1.0.0
│  └─ webpack@npm:5.70.0 [b5b1e] (via npm:5.70.0 [b5b1e]) 👈
│
├─ @storybook/builder-webpack4@npm:6.4.19
│  └─ webpack@npm:4.46.0 (via npm:4)
.
.

│  └─ webpack@npm:5.71.0 (via npm:^5.9.0)  👈
│
├─ @storybook/manager-webpack5@npm:6.4.19 [7f8c1]
│  └─ webpack@npm:5.71.0 [0dc39] (via npm:^5 [0dc39]) 👈
.
.

The solution for now, is to force the resolution of webpack 5, but we should issue a patch with the updated webpack version so theres no mismatch. Note that its not the updated webpack that solves the problem, its definitely a storybook thing, because even if you set the webpack version to 5.70.0 it still works fine

In your root package.json

  "resolutions": {
    "webpack": "5.71.0"
  },

Walkthrough here: https://s.tape.sh/fMzJpPyA

[dac09]

Confirming that upgrading to the latest canary fixes it in the reproduction Gitpod!