2

I have a NextJS app I'm working on developing. I'm currently trying out Storybook to develop the various components in isolation of each other.

If I run the app via npm run dev then WebStorm will perfectly stop at my breakpoints, but if I run the app in Storybook via npm run storybook (a script for storybook dev -p 6006) I can do seemingly nothing to get it to stop at breakpoints.

I've tried attaching to an already running browser, installing Chrome to replace Firefox as the WebStorm debugger only supports Chromium-based browsers. I've checked I don't use webpack or any source map problem (debugging the app normally works anyway).

Is it even possible to attach a debugger to Storybook, or am I approaching this problem from completely the wrong angle?

In the meantime I'm going to debug my components out of isolation as part of the full app, but any pointers on getting the WebStorm debugger to attach to Storybook or troubleshooting this would be greatly appreciated.

Improve this question
2
  • Same issue. Debugger runs but won't stop on breakpoints. Are you using WSL? Commented Apr 11, 2024 at 2:30
  • I'm afraid not - I'm just running it natively on Windows with Node 20.10 and Webstorm 2023.3.2 Commented Apr 11, 2024 at 8:36
Related questions
7
WebStorm react-native debug not working
0
WebStorm + webpacker debugging
2
Debugging in WebStorm with Vue.js
Load 2 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.