René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Bug]: use of isomorphic-unfetch breaks storybook-next build","articleBody":"We're experiencing a problem using `isomorphic-unfetch` in `storybook` together with `nextjs`. Even though it works fine in the `next` build, importing `isomorphic-unfetch` in a component in `storybook` causes several errors.\r\n```\r\nModule not found: Error: Can't resolve 'unfetch' in '/Users/martaver/Projects/repro/node_modules/isomorphic-unfetch'\r\n```\r\nand several of:\r\n```\r\nModule build failed: UnhandledSchemeError: Reading from \"node:buffer\" is not handled by plugins (Unhandled scheme).\r\nWebpack supports \"data:\" and \"file:\" URIs by default.\r\nYou may need an additional plugin to handle \"node:\" URIs.\r\n```\r\n\r\nI've documented the problem and provided a full repro in the `storybook` repo, since it seems to be caused by a difference between how `storybook` and `next` are built, but I thought I'd also flag the issue here, in case the authors might have some insight:\r\n\r\nhttps://github.com/storybookjs/storybook/issues/23700","author":{"url":"https://github.com/martaver","@type":"Person","name":"martaver"},"datePublished":"2023-08-03T11:15:36.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/174/unfetch/issues/174"}