styleguidist build returns:

styleguidist server runs fine:

It's not a priority issue but would be nice to have a clean build. I don't mind searching for a solution if anyone can point me in the right direction?
@prjctnxt did you solve this? I am having the same issue.
I also have the same problem and I'm always looking for the solution
Making sure this one doesn't close without something.
@prjctnxt did you solve this? I am having the same issue.
I don't remember finding a solution (it's been a while).
The issue was closed because I thought it was spammy; which appears was a mistake (whoops).
Having same problem...
I am having a similar issue and I am using the default set up with Create-React-App
build/main.9b1c9dda.js contains invalid source map
build/bundle.5339aa43.js contains invalid source map
The comment file "build/2.ab21be89.js.LICENSE.txt" conflicts with an existing asset, this may lead to code corruption, please use a different name
I have exactly the same issue as @YapiKamilAqil 馃槩
I'm having this same issue as well, I've been going at this one for days and can't seem to figure out what is going on...
Well, i just ignore the logs for now the build is still servable.
Was able to solve this problem by explicitly creating my own babel config file and including my webpack config in the styleguide.config.js
I'm also experiencing this issue. My project was bootstrapped using create-react-app so I'm weary of messing with webpack.
I am getting this error: The comment file "build/main.f1f51186.js.LICENSE.txt" conflicts with an existing asset, this may lead to code corruption, please use a different name when running styleguidist build.
It is failing to compile, but styleguidist server runs fine.

Same issue for my part
We had to turn off the optimization in the styleguide config's webpack config:
...
webpackConfig: {
optimization: undefined
}
Hey, I fix it like this:
webpackConfig: {
devtool: 'eval-source-map',
...
}
馃槾 This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week without any further activity. Consider opening a pull request if you still have this issue or want this feature.
Experiencing the same issue with a CRA app.
Most helpful comment