Better copy for the empty state message

[okonet]

Right now, if SG wasn't able to locate components at the provided paths, it will try to locate them in the default path. If this also fails, the empty message will be displayed saying:

We couldn't find any components defined in your style guide config or using the default pattern src/components/**/*.js.

I believe this is a bit confusing since it displays only the default path explicitly. This made me think my config wasn't read by SG. Reading the whole message carefully explained it but I think this can be improved by showing the list of all paths where SG was trying to locate components:

We looked at following paths:
- [path 1 from user config]
- [path 2 from user config]
- [fallback default path]
but couldn't find any components. Please make sure you have your components there and try again.

[sapegin]

Yeah, that was the plan, just haven’t have time to implement it yet ;-) It won’t use the default value if you have your own patterns in the config.

[okonet]

So this means the message is even more confusing then :)

[sapegin]

Yeah 😬

[sapegin]

Call it MVP ;-)

[KumarKelashMeghwar]

I have the same error issue. How to make it work? I have added --config config/styleguidist.config.js but still getting same I dont know wh

y

`this is my config file

    const { version } = require("../package.json");

module.exports = {
title: "Styleguidist Tutorial",
version,
components: "../src/components/[A-Z]/*.js",
ignore: ["/src/test.js"],

webpackConfig: {
module: {
rules: [
{
test: /.jsx?$/,
exclude: /node_modules/,
loader: "babel-loader",
},
],
},
},
};

`