question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Compiling manager fails to: comment file "xxx.worker.js.LICENSE.txt" conflicts with an existing asset

See original GitHub issue

Describe the bug

When running build-storybook -c .storybook -o storybook-static, the build fails to “Compiling manager” step. This only happened with the recent 6.0.0-rc.X versions. I tried with rc 1, 10, 11, and 14. All failed to the same step

The current workaround is to use 6.0.0-beta.20. I checked what version you use in Storybook design system: https://github.com/storybookjs/design-system/blob/master/package.json and copied the same.

To Reproduce Steps to reproduce the behavior:

Run build-storybook -c .storybook -o storybook-static with new versions of major 6. Console will output this error:

12:25:47 PM: info => Compiling manager..
12:26:25 PM: ERR! => Failed to build the manager
12:26:25 PM: ERR! The comment file "1cd777c4fb4f5c3aa725.worker.js.LICENSE.txt" conflicts with an existing asset, this may lead to code corruption, please use a different name
12:26:25 PM: (node:1637) UnhandledPromiseRejectionWarning: [object Object]
12:26:25 PM: (node:1637) 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(). (rejection id: 1)
12:26:25 PM: (node:1637) [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.

Expected behavior

I would expect the build to succeed.

Code snippets Our .storybook/main.js:

module.exports = {
  stories: ['../src/**/*.stories.@(ts|tsx|js|jsx|mdx)'],
  addons: [
    '@storybook/addon-knobs/register',
    'storybook-addon-designs/register',
    '@storybook/addon-actions',
    '@storybook/addon-links',
    {
      name: '@storybook/addon-docs',
      options: {
        configureJSX: true,
        babelOptions: {},
        sourceLoaderOptions: null,
      },
    },
  ],
};

System:

Environment Info:

  System:
    OS: Linux 5.7 Fedora 32 (Workstation Edition) 32 (Workstation Edition)
    CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
  Binaries:
    Node: 12.18.0 - ~/.nvm/versions/node/v12.18.0/bin/node
    npm: 6.14.4 - ~/.nvm/versions/node/v12.18.0/bin/npm
  Browsers:
    Chrome: 84.0.4147.89
    Firefox: 78.0.2
  npmPackages:
    @storybook/addon-actions: 6.0.0-rc.14 => 6.0.0-rc.14 
    @storybook/addon-docs: 6.0.0-rc.14 => 6.0.0-rc.14 
    @storybook/addon-knobs: 6.0.0-rc.14 => 6.0.0-rc.14 
    @storybook/addon-links: 6.0.0-rc.14 => 6.0.0-rc.14 
    @storybook/addons: 6.0.0-rc.14 => 6.0.0-rc.14 
    @storybook/preset-typescript: ^3.0.0 => 3.0.0 
    @storybook/react: 6.0.0-rc.14 => 6.0.0-rc.14 

Additional context

Some similar issues I found:

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:11 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
shilmancommented, Jul 23, 2020

I removed storybook-addon-designs and the error went away. @pocka can you help here?

1reaction
pockacommented, Jul 24, 2020

Probably https://github.com/webpack-contrib/worker-loader/issues/260.

The addon depends on react-pdf (I know I should have put the dependency into peerDependencies), which uses Worker script imported via worker-loader. Since I’m not sure which package depends on worker-loader, a temporary workaround until a fix comes to the loader is pinning terser-webpack-plugin to v3.0.6.

with Yarn workspace
// package.json
{
  // ...
  "resolutions": {
    "terser-webpack-plugin": "3.0.6"
  }
}
with npm
$ npm i -D terser-webpack-plugin@3.0.6

If none of the above workarounds works, please tell me.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting Omnibus GitLab installation issues
Some users report that running gitlab-rake assets:precompile does not work with the omnibus packages. The short answer to this is: do not run...
Read more >
Bug listing with status RESOLVED with resolution TEST ...
Bug:233 - "Emacs segfaults when merged through the sandbox." status:RESOLVED resolution:TEST-REQUEST severity:critical · Bug:3888 - "yenta_socket module not ...
Read more >
Webpack 5 release (2020-10-10)
Webpack 5 has now native support for modules representing assets. These modules will either emit a file into the output folder or inject...
Read more >
Unity 2022.2.0b11
Editor: Job worker threads will now prefer executing jobs scheduled ... IL2CPP: Fixed compilation error that occurred when a enum was passed ...
Read more >
Information | Instructions for Authors - MDPI
Manuscript Submission Overview. Types of Publications. Information has no restrictions on the length of manuscripts, provided that the text is concise and ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found