Replies: 2 comments
-
I normally just use a chrome launch config, with the url of my running Storybook. This is from one of my projects. {
"type": "chrome",
"request": "launch",
"name": "Launch Chrome against localhost",
"url": "http://localhost:6006/",
"webRoot": "${workspaceFolder}",
"userDataDir": "${workspaceFolder}/.vscode/.chrome-user-dir",
}, I haven't done this in a while, so I just checked that it still works. The only problem that I noticed is that my VSCode is adding my breakpoints to the wrong line. That could just be a problem with my project though and my not be related to anything Storybook is doing. I just haven't looked into why the breakpoint lines numbers are off for me, yet. I don't know if there is something specific that needs to be configured, so if it matters, I am using Angular and haven't added anything extra to allow the debugger to work, that I know of. |
Beta Was this translation helpful? Give feedback.
-
I know this is kind of an older thread, but I also had this issue and found a solution. It's quite possible that my solution is super specific to my setup, so apologies if it doesn't work. I'm on I put the following config in my launch.json: {
"type": "firefox",
"request": "launch",
"name": "Storybook Debug Firefox",
"url": "http://localhost:6006", // Your Storybook URL here
"webRoot": "${workspaceRoot}",
"suggestPathMappingWizard": true,
} I did the following steps to get it to work properly:
This is a bit convoluted but it worked in the end! I spent another couple hours attempting to figure out Chrome, but even with the same exact path mappings I just couldn't figure it out 😅. Hopefully this helps someone else! |
Beta Was this translation helpful? Give feedback.
-
Summary
At the moment breakpoints in my project components inside storyboard cant bind. How to setup launch.js to make it work?
Additional information
No response
Create a reproduction
No response
Beta Was this translation helpful? Give feedback.
All reactions