storybook: The latest version of Storybook couldn't be fetched (in static build)

Describe the bug In the static build of Storybook, the latest version of Storybook cannot be fetched. It doesn’t matter if I open the index.html locally or open the deployed version on my server.

To Reproduce Steps to reproduce the behavior:

  1. Build Storybook
  2. Open storybook-static/index.html in your browser
  3. Got to the “About your Storybook” page
  4. Error: Oops! The latest version of Storybook couldn't be fetched.

Screenshots Bildschirmfoto 2020-08-04 um 17 49 50@2x

Expected behavior Fetch the current version of Storybook and display the information like in the served version: Bildschirmfoto 2020-08-04 um 18 05 23

System: npx -p @storybook/cli@next sb info (or without @next) is throwing an error:

Environment Info:
(node:45923) UnhandledPromiseRejectionWarning: TypeError: (e || []).filter is not a function
    at /Users/<my name>/.npm/_npx/45915/lib/node_modules/@storybook/cli/node_modules/envinfo/dist/envinfo.js:1:73314
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Promise.all (index 6)
(node:45923) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:45923) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 4
  • Comments: 16 (9 by maintainers)

Most upvoted comments

Probably not a big surprise, but just wanted to mention it: It’s still not working in v7.

Yeah… the deployed (build) version of sb always throws this error. currently on 6.3.12 Screen Shot 2021-10-29 at 2 14 13 PM