Storybook: problem with custom config folder instead of .storybook

[devniel]

Hello,

Describe the bug
I'm getting an error on remote platforms (on localhost runs without problems)
(node:901) UnhandledPromiseRejectionWarning: Error: => Create a storybook config file in "config/storybook/config.{ext}". when using a custom configuration folder an setting it with the -c argument.

To Reproduce
I'm building my project on a PaaS, where there is necessary to provide a script to build the project, in my case it's like this.

#!/bin/bash
npm config delete prefix
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.11/install.sh | bash
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion
nvm install 8.11.4
npm install yarn -g
yarn install
yarn build
yarn build-storybook

My project structure is:

config
 storybook
   config.js
   webpack.config.js
package.json

I'm using a custom configuration folder, so my build-storybook script executes this command:

build-storybook -c config/storybook -o storybook (I've also used ./config/storybook)

But it returns the described error.

The thing is that when using the default .storybook on the root folder, and setting the script to build-storybook -o storybook it builds without problems. I'm thinking that there is a problem with the resolution of the given custom folder path.

Expected behavior
Build storybook without problems.

Screenshots

[shilman]

What version?

[devniel]

Hi, I'm using @storybook/react: "^5.0.10"

[shilman]

Strange. Our examples/official-storybook uses a custom path:

https://github.com/storybooks/storybook/blob/master/examples/official-storybook/package.json#L6

And it works fine:

https://storybooks-official.netlify.com/

Do you have a repro you can share?

[stale[bot]]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[bife1]

The same bug, any suggestions?

[stale[bot]]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[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!

[Gilbert-Adu]

having the same bug. anyone with suggestions as to how to solve this?