You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In fresh nextjs/storybook project, source maps don't work. When clicking on source references in chrome dev tools, received the following error message:
Could not load content for webpack://my-app/ (Fetch through target failed: Unsupported URL scheme; Fallback: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME)
I am seeing the same behavior after upgrading from v7 -> v8. This only happens for *.stories.tsx files however, all other source maps load correctly. I believe this has something to do with how the stories are lazy loaded.
This seems to have improved very slightly but still be broken as of v8.1.0-alpha.6. I assume the related change is #26676.
Could not load content for webpack://my-app/src/stories/Button.tsx (Fetch through target failed: Unsupported URL scheme; Fallback: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME)
I'm seeing this issue in 7.6.17 and I haven't updated my Storybook version in a long time. It just suddenly started failing. What's actually happening, if I start on the landing page, once I hover over a link in the side bar menu, sourcemaps fail to load in the background. I've tried disabling all my extension, but I'm still seeing the issue. I'm wondering if it was a browser update that's the issue. I'm seeing this issue in Safari, Chrome, and Brave, but not an issue in Firefox. It certainly seems to be related to lazy loading in Chromium browsers.
Describe the bug
In fresh nextjs/storybook project, source maps don't work. When clicking on source references in chrome dev tools, received the following error message:
To Reproduce
Minimal repro repo
nvm use 20
npx create-next-app@latest
// all defaultcd my-app
npx storybook@latest init
// all defaultconsole.log('test');
to the automatically created Button componentSystem
Additional context
No response
The text was updated successfully, but these errors were encountered: