Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@storybook/core – dll/storybook_ui-manifest.json does not exist after installation #9763

Closed
sawyerh opened this issue Feb 5, 2020 · 2 comments

Comments

@sawyerh
Copy link

sawyerh commented Feb 5, 2020

Describe the bug
After bootstrapping a project with @storybook/react v5.3.11 and running start-storybook -p 6006, I received the following error in the CLI:

TypeError: Cannot read property 'toJson' of null
    at Watching.handler (/[my project]/node_modules/@storybook/core/dist/server/dev-server.js:84:17)

After adding additional logging to dev-server.js to get some more useful debug info, it appears that this is due to the following error:

Error: ENOENT: no such file or directory, open '/[my project]/node_modules/@storybook/core/dll/storybook_ui-manifest.json'

When I look in the @storybook/core/dll/ directory, there is nothing in it.

I've tried deleting my node_modules and installing from scratch, but get the same results.

System:

  System:
    OS: macOS 10.15.2
    CPU: (4) x64 Intel(R) Core(TM) i5-6267U CPU @ 2.90GHz
  Binaries:
    Node: 12.13.0 - ~/.nvm/versions/node/v12.13.0/bin/node
    Yarn: 1.19.1 - /usr/local/bin/yarn
    npm: 6.13.7 - ~/.nvm/versions/node/v12.13.0/bin/npm
  Browsers:
    Chrome: 80.0.3987.87
    Firefox: 71.0
    Safari: 13.0.4
  npmPackages:
    @storybook/react: ^5.3.11 => 5.3.11

Additional context
Potentially related to #9707?

@sawyerh sawyerh changed the title Storybook not working due to dll/storybook_ui-manifest.json not existing @storybook/core – dll/storybook_ui-manifest.json does not exist after installation Feb 5, 2020
@sawyerh
Copy link
Author

sawyerh commented Feb 5, 2020

Looks like this was fixed in 5.3.12

@shilman
Copy link
Member

shilman commented Feb 5, 2020

Definitely related to #9707 - I need to be super careful with the release until this gets fixed. cc @ndelangen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants