[NETLIFY] "build.command" failed • Command failed with exit code 1: build-storybook -s ./public

Describe the bug I installed storybook on my project. It works well on local using yarn storybook. But when I try to deploy on Netlify I have the following error :

2:20:13 PM: ┌─────────────────────────────┐
2:20:13 PM: │   "build.command" failed    │
2:20:13 PM: └─────────────────────────────┘
2:20:13 PM: ​
2:20:13 PM:   Error message
2:20:13 PM:   Command failed with exit code 1: build-storybook -s ./public
2:20:13 PM: ​
2:20:13 PM:   Error location
2:20:13 PM:   In Build command from Netlify app:
2:20:13 PM:   build-storybook -s ./public
2:20:13 PM: ​
2:20:13 PM:   Resolved config
2:20:13 PM:   build:
2:20:13 PM:     command: build-storybook -s ./public
2:20:13 PM:     commandOrigin: ui
2:20:13 PM:     publish: /opt/build/repo/public

To Reproduce Steps to reproduce the behavior:

I tried these but none of them worked.

yarn build-storybook

build-storybook -s ./public"

NODE_ENV=production build-storybook -s ./public

package.json

  "scripts": {
    "start": "gatsby clean && gatsby develop --port 8003",
    "build": "gatsby clean && gatsby build",
    "storybook": "NODE_ENV=production start-storybook -p 6006 -s ./public",
    "build-storybook": "NODE_ENV=production build-storybook -s ./public"
  }

Expected behavior Build success

System:

  System:
    OS: macOS Mojave 10.14.5
    CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
  Binaries:
    Node: 10.16.0 - /usr/local/opt/node@10/bin/node
    Yarn: 1.19.2 - ~/.yarn/bin/yarn
    npm: 6.9.0 - /usr/local/opt/node@10/bin/npm
  Browsers:
    Firefox: 78.0.1
    Safari: 13.1.1
  npmPackages:
    @storybook/addon-actions: ^5.3.19 => 5.3.19 
    @storybook/addon-links: ^5.3.19 => 5.3.19 
    @storybook/addons: ^5.3.19 => 5.3.19 
    @storybook/react: ^5.3.19 => 5.3.19 

[Steffi3rd]

Looks like every deploy on storybook official netlify are failed : https://app.netlify.com/sites/storybooks-official/deploys 🤔

[stale[bot]]

Hey there, it’s me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!