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.

Sign up for GitHub

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

Jump to bottom

[Bug]: npx sb@next upgrade --prerelease fails #21872

Closed
rezoled opened this issue Apr 2, 2023 · 21 comments · Fixed by #21947 or #22039
Closed

[Bug]: npx sb@next upgrade --prerelease fails #21872

rezoled opened this issue Apr 2, 2023 · 21 comments · Fixed by #21947 or #22039
Assignees
@valentinpalkovic
Labels
bug cli

Comments

@rezoled
Copy link

rezoled commented Apr 2, 2023

Describe the bug

On an existing SB repo, I tried to upgrade from RC to 7 by running the upgrade action.
Here is the result:

*****@ip-***** ***** % npx sb@next upgrade --prerelease
Need to install the following packages:
  sb@7.0.0
Ok to proceed? (y) y
 • Checking for latest versions of '@storybook/*' packagesinfo ,Upgrading /Users/*****/*****/*****/package.json
info 
info All dependencies match the @next package versions :)
info ,npm WARN exec The following package was not found and will be installed: npm-check-updates@16.10.0
info npm WARN deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
info 
info 
info ,Upgrading /Users/*****/*****/*****/package.json
info 
info No dependencies.
info ,
 • Installing upgrades • Preparing to install dependencies. ✓



> *****@0.0.0 postinstall
> ngcc --properties es2015 browser module main


> *****@0.0.0 prepare
> husky install

husky - Git hooks installed

removed 1 package, and audited 3845 packages in 12s

384 packages are looking for funding
  run `npm fund` for details

7 vulnerabilities (4 moderate, 1 high, 2 critical)

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
. ✓
🔎 checking possible migrations..

🔎 found a 'github-flavored-markdown-mdx' migration:
╭ Automigration detected ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                                                                                │
│   In MDX1 you had the option of using GitHub flavored markdown.                                                                                │
│                                                                                                                                                │
│   Storybook 7.0 uses MDX2 for compiling MDX, and thus no longer supports GFM out of the box.                                                   │
│   Because of this you need to explicitly add the GFM plugin in the addon-docs options:                                                         │
│   https://storybook.js.org/docs/7.0/react/writing-docs/mdx#lack-of-github-flavored-markdown-gfm                                                │
│                                                                                                                                                │
│   We recommend you follow the guide on the link above, however we can add a temporary storybook addon that helps make this migration easier.   │
│   We'll install the addon and add it to your storybook config.                                                                                 │
│                                                                                                                                                │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
✔ Do you want to run the 'github-flavored-markdown-mdx' migration on your project? … no
ERR! Error
ERR!     at NPMProxy.executeCommand (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:1665)
ERR!     at NPMProxy.findInstallations (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:2299)
ERR!     at automigrate (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:309:1066)
ERR!     at async doUpgrade (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:382:2893)
ERR!     at async withTelemetry (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/core-server/dist/index.js:27:3469)
ERR!     at async upgrade (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:382:3336)
ERR!  Error
ERR!     at NPMProxy.executeCommand (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:1665)
ERR!     at NPMProxy.findInstallations (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:2299)
ERR!     at automigrate (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:309:1066)
ERR!     at async doUpgrade (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:382:2893)
ERR!     at async withTelemetry (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/core-server/dist/index.js:27:3469)
ERR!     at async upgrade (/Users/*****/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:382:3336)

To Reproduce

No response

System

No response

Additional context

No response
@rezoled
Copy link
Author

rezoled commented Apr 2, 2023 •
edited

After a bit of debugging, it seems like the upgrade code tries to run the following action using spawn.sync:
npm ls --json --depth=99
the code checks:

if(commandResult.status!==0)throw new Error(commandResult.stderr??"")

And from what I noticed was that commandResult.status is equal to null
Since null is not equal to 0, an error is thrown, and since there is not actual error emitted from NPM the error message is empty.

More investigation yielded that the NPM command was killed by SIGTERM, I have no idea why.
When running npm ls --json --depth=99 it works by outputting a tree of dependencies.

Even more investigation. I modified the code to print the output from NPM:

 error: Error: spawnSync /bin/sh ENOBUFS
      at __node_internal_captureLargerStackTrace (node:internal/errors:490:5)
      at __node_internal_errnoException (node:internal/errors:620:12)
      at Object.spawnSync (node:internal/child_process:1110:20)
      at Object.spawnSync (node:child_process:871:24)
      at spawnSync (/Users/roypeled/.npm/_npx/eebb2d3a7d26a7f1/node_modules/cross-spawn/index.js:26:23)
      at NPMProxy.executeCommand (/Users/roypeled/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:1549)
      at NPMProxy.findInstallations (/Users/roypeled/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:2386)
      at automigrate (/Users/roypeled/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:309:1066)
      at async doUpgrade (/Users/roypeled/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:382:2893)
      at async withTelemetry (/Users/roypeled/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/core-server/dist/index.js:27:3469)
      at async upgrade (/Users/roypeled/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:382:3336)

I seems like spawn sync has a default output buffer of 200kb (https://stackoverflow.com/questions/63796633/spawnsync-bin-sh-enobufs), maybe it would be better to change the call to async (not sure if it would solve it) or don't pipe the output at all.

Furthermore, the error was not at all printed to the console, so the pipe got lost in the way.

@shilman shilman added cli and removed needs triage labels Apr 3, 2023
@PhHitachi
Copy link

i face same issues with next.js 13

"devDependencies": {
    "@babel/core": "^7.21.4",
    "@storybook/addon-actions": "^7.0.1",
    "@storybook/addon-essentials": "^7.0.1",
    "@storybook/addon-interactions": "^7.0.1",
    "@storybook/addon-links": "^7.0.1",
    "@storybook/addon-mdx-gfm": "^7.0.1",
    "@storybook/nextjs": "^7.0.1",
    "@storybook/react": "^7.0.1",
    "@storybook/testing-library": "^0.1.0",
    "babel-loader": "^8.3.0",
    "eslint-plugin-storybook": "^0.6.11",
    "storybook": "^7.0.1"
 }

image

@dsousa12
Copy link

dsousa12 commented Apr 4, 2023

i face same issues with next.js 13

"devDependencies": {
    "@babel/core": "^7.21.4",
    "@storybook/addon-actions": "^7.0.1",
    "@storybook/addon-essentials": "^7.0.1",
    "@storybook/addon-interactions": "^7.0.1",
    "@storybook/addon-links": "^7.0.1",
    "@storybook/addon-mdx-gfm": "^7.0.1",
    "@storybook/nextjs": "^7.0.1",
    "@storybook/react": "^7.0.1",
    "@storybook/testing-library": "^0.1.0",
    "babel-loader": "^8.3.0",
    "eslint-plugin-storybook": "^0.6.11",
    "storybook": "^7.0.1"
 }

image

Same for me

@caomicc
Copy link

caomicc commented Apr 4, 2023

+1 Also happening to me

✅ Adding "@storybook/addon-mdx-gfm" addon
✅ ran github-flavored-markdown-mdx migration
ERR! Error: npm ERR! code ELSPROBLEMS
ERR! npm ERR! invalid: @storybook/mdx1-csf@0.0.1 /Users/XXXXXXXXX/Documents/git/magma/node_modules/@storybook/mdx1-csf
ERR! npm ERR! invalid: cypress@12.8.1 /Users/XXXXXXXXX/Documents/git/magma/node_modules/cypress
ERR! npm ERR! invalid: glob@7.1.7 /Users/XXXXXXXXX/Documents/git/magma/packages/ui/node_modules/glob
ERR! npm ERR! missing: get-tsconfig@^4.2.0, required by eslint-import-resolver-typescript@3.5.3
ERR! npm ERR! missing: synckit@^0.8.4, required by eslint-import-resolver-typescript@3.5.3
ERR! npm ERR! invalid: acorn@7.4.1 /Users/XXXXXXXXX/Documents/git/magma/node_modules/acorn
ERR! npm ERR! invalid: react@18.2.0 /Users/XXXXXXXXX/Documents/git/magma/node_modules/react
ERR! npm ERR! invalid: @storybook/mdx2-csf@1.0.0 /Users/XXXXXXXXX/Documents/git/magma/node_modules/@storybook/mdx2-csf
ERR! npm ERR! invalid: webpack@5.76.2 /Users/XXXXXXXXX/Documents/git/magma/node_modules/webpack
ERR! npm ERR! invalid: react-dom@18.2.0 /Users/XXXXXXXXX/Documents/git/magma/node_modules/react-dom
ERR! npm ERR! missing: w3c-hr-time@^1.0.2, required by jsdom@19.0.0
ERR! npm ERR! missing: terminal-link@^2.0.0, required by @jest/reporters@28.1.3
ERR! {
ERR!   "error": {
ERR!     "code": "ELSPROBLEMS",
ERR!     "summary": "invalid: @storybook/mdx1-csf@0.0.1 /Users/XXXXXXXXX/Documents/git/magma/node_modules/@storybook/mdx1-csf\ninvalid: cypress@12.8.1 /Users/XXXXXXXXX/Documents/git/magma/node_modules/cypress\ninvalid: glob@7.1.7 /Users/XXXXXXXXX/Documents/git/magma/packages/ui/node_modules/glob\nmissing: get-tsconfig@^4.2.0, required by eslint-import-resolver-typescript@3.5.3\nmissing: synckit@^0.8.4, required by eslint-import-resolver-typescript@3.5.3\ninvalid: acorn@7.4.1 /Users/XXXXXXXXX/Documents/git/magma/node_modules/acorn\ninvalid: react@18.2.0 /Users/XXXXXXXXX/Documents/git/magma/node_modules/react\ninvalid: @storybook/mdx2-csf@1.0.0 /Users/XXXXXXXXX/Documents/git/magma/node_modules/@storybook/mdx2-csf\ninvalid: webpack@5.76.2 /Users/XXXXXXXXX/Documents/git/magma/node_modules/webpack\ninvalid: react-dom@18.2.0 /Users/XXXXXXXXX/Documents/git/magma/node_modules/react-dom\nmissing: w3c-hr-time@^1.0.2, required by jsdom@19.0.0\nmissing: terminal-link@^2.0.0, required by @jest/reporters@28.1.3",
ERR!     "detail": ""
ERR!   }
ERR! }
ERR! 
ERR!     at NPMProxy.executeCommand (/Users/XXXXXXXXX/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:1669)
ERR!     at NPMProxy.findInstallations (/Users/XXXXXXXXX/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:2303)
ERR!     at automigrate (/Users/XXXXXXXXX/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:317:1066)
ERR!     at async doUpgrade (/Users/XXXXXXXXX/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:390:2893)
ERR!     at async withTelemetry (/Users/XXXXXXXXX/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/core-server/dist/index.js:35:3422)
ERR!     at async upgrade (/Users/XXXXXXXXX/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:390:3336)

@leschdom
Copy link

leschdom commented Apr 5, 2023 •
edited

When running npm ls --json --depth=99 it works by outputting a tree of dependencies.

This was added in here: 106b68f#diff-d0f1791b397d5217ce251c489ba1f69d64230e5850d03a380d1bc2ed687b7e0cR38

We also face this issue and the migration worked for me when I used 7.0.0-rc.8. But this version introduced this change https://github.com/storybookjs/storybook/releases/tag/v7.0.0-rc.10 (#21791). Maybe this helps for further analysis.

@valentinpalkovic valentinpalkovic mentioned this issue Apr 5, 2023
Merged
5 tasks
@shilman
Copy link
Member

shilman commented Apr 5, 2023

Yo-ho-ho!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.1.0-alpha.0 containing PR #21947 that references this issue. Upgrade today to the @next NPM tag to try it out!

npx sb@next upgrade --prerelease

@AlexSapoznikov
Copy link

Yo-ho-ho!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.1.0-alpha.0 containing PR #21947 that references this issue. Upgrade today to the @next NPM tag to try it out!

npx sb@next upgrade --prerelease

This still results in ELSPROBLEMS

image

@ndelangen
Copy link
Member

@valentinpalkovic what do you think we should do?

@shilman
Copy link
Member

shilman commented Apr 12, 2023 •
edited

Olé!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.0.3 containing PR #21947 that references this issue. Upgrade today to the @latest NPM tag to try it out!

npx sb@latest upgrade

@rebeljoi
Copy link

Olé!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.0.3 containing PR #21947 that references this issue. Upgrade today to the @latest NPM tag to try it out!

npx sb@latest upgrade

@shilman Still not working with 7.0.3.

image

@valentinpalkovic
Copy link
Contributor

@yannbf Could you take another look at the implementation of findInstallations?

@valentinpalkovic
Copy link
Contributor

@rebeljoi Have you executed npx sb@latest upgrade for the upgrade?

@rebeljoi
Copy link

@rebeljoi Have you executed npx sb@latest upgrade for the upgrade?

@valentinpalkovic Yes. To me it looks like problem is that this line will still throw an error that isn't caught.

@valentinpalkovic valentinpalkovic mentioned this issue Apr 12, 2023
Merged
5 tasks
@shilman
Copy link
Member

shilman commented Apr 12, 2023

Yay!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.1.0-alpha.2 containing PR #22039 that references this issue. Upgrade today to the @future NPM tag to try it out!

npx sb@next upgrade --tag future

@carlosrsabreu
Copy link

Yay!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.1.0-alpha.2 containing PR #22039 that references this issue. Upgrade today to the @future NPM tag to try it out!

npx sb@next upgrade --tag future

Hello,

I run that command and I got this error:

ERR! Error
ERR!     at NPMProxy.executeCommand (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:1669)
ERR!     at NPMProxy.findInstallations (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:2371)
ERR!     at automigrate (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:317:1066)
ERR!     at async doUpgrade (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:390:2893)
ERR!     at async withTelemetry (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/core-server/dist/index.js:35:3422)
ERR!     at async upgrade (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:390:3336)
ERR!  Error
ERR!     at NPMProxy.executeCommand (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:1669)
ERR!     at NPMProxy.findInstallations (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:39:2371)
ERR!     at automigrate (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:317:1066)
ERR!     at async doUpgrade (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:390:2893)
ERR!     at async withTelemetry (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/core-server/dist/index.js:35:3422)
ERR!     at async upgrade (/Users/*******/.npm/_npx/eebb2d3a7d26a7f1/node_modules/@storybook/cli/dist/generate.js:390:3336)

@ReihaneB
Copy link

Same error @carlosrsabreu, try running npx storybook@future upgrade --tag future

@carlosrsabreu
Copy link

carlosrsabreu commented Apr 12, 2023 •
edited

Same error @carlosrsabreu, try running npx storybook@future upgrade --tag future

Yeah, it worked! 🚀 Thank you!

@GrumpyMeow
Copy link

Resolved also the same error on my code-base.
Thanks!.

@shilman
Copy link
Member

shilman commented Apr 12, 2023

Crikey!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.0.4 containing PR #22039 that references this issue. Upgrade today to the @latest NPM tag to try it out!

npx sb@latest upgrade

@nshimiye
Copy link

nshimiye commented Apr 12, 2023 •
edited

@valentinpalkovic So in the PR #22039, it looks like the error is being ignored.
Is it safe to ignore it?

i.e. would there be a case where npx sb@latest upgrade command corrupts the code because we're letting it continue to run even if it produced errors?

@elmaurer
Copy link

I ran the new command and the error still occurs.

$ npx sb@latest upgrade
Need to install the following packages:
  sb@latest
Ok to proceed? (y) y
 • Checking for latest versions of '@storybook/*' packagesinfo ,Upgrading C:\Users\*****\Projects\*****\**********\package.json
info 
info  @storybook/addon-a11y               ^7.0.2  →  ^7.0.5
info  @storybook/addon-actions            ^7.0.2  →  ^7.0.5
info  @storybook/addon-docs               ^7.0.2  →  ^7.0.5
info  @storybook/addon-essentials         ^7.0.2  →  ^7.0.5
info  @storybook/addon-interactions       ^7.0.2  →  ^7.0.5
info  @storybook/addon-links              ^7.0.2  →  ^7.0.5
info  @storybook/addon-mdx-gfm            ^7.0.2  →  ^7.0.5
info  @storybook/addon-viewport           ^7.0.2  →  ^7.0.5
info  @storybook/node-logger              ^7.0.2  →  ^7.0.5
info  @storybook/preset-create-react-app  ^7.0.2  →  ^7.0.5
info  @storybook/react                    ^7.0.2  →  ^7.0.5
info  @storybook/react-webpack5           ^7.0.2  →  ^7.0.5
info  @storybook/theming                  ^7.0.2  →  ^7.0.5
info  storybook                           ^7.0.2  →  ^7.0.5
info
info Run npm install to install new versions.
info ,npm WARN exec The following package was not found and will be installed: npm-check-updates@latest
info
info
info ,Upgrading C:\Users\*****\Projects\*****\**********\package.json
info
info No dependencies.
info ,
 • Installing upgrades • Preparing to install dependencies. ✓



removed 5 packages, changed 64 packages, and audited 2560 packages in 18s

408 packages are looking for funding
  run `npm fund` for details

6 high severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
. ✓
🔎 checking possible migrations..
ERR! Error: npm ERR! code ELSPROBLEMS
ERR! npm ERR! invalid: typescript@5.0.3 C:\Users\*****\Projects\*****\**********\node_modules\typescript
ERR! npm ERR! invalid: acorn@7.4.1 C:\Users\*****\Projects\*****\**********\node_modules\acorn
ERR! npm ERR! invalid: glob@7.2.3 C:\Users\*****\Projects\*****\**********\node_modules\glob
ERR! npm ERR! invalid: ajv@6.12.6 C:\Users\*****\Projects\*****\**********\node_modules\ajv
ERR! npm ERR! invalid: rollup@3.20.2 C:\Users\*****\Projects\*****\**********\node_modules\rollup
ERR! {
ERR!   "error": {
ERR!     "code": "ELSPROBLEMS",
ERR!     "summary": "invalid: typescript@5.0.3 C:\\Users\\*****\\Projects\\*****\\**********\\node_modules\\typescript\r\ninvalid: acorn@7.4.1 C:\\Users\\*****\\Projects\\*****\\**********\\node_modules\\acorn\r\ninvalid: glob@7.2.3 C
:\\Users\\*****\\Projects\\*****\\**********\\node_modules\\glob\r\ninvalid: ajv@6.12.6 C:\\Users\\*****\\Projects\\*****\\**********\\node_modules\\ajv\r\ninvalid: rollup@3.20.2 C:\\Users\\*****\\Projects\\*****\\**********\\node_modules\\rollup",
ERR!     "detail": ""
ERR!   }
ERR! }
ERR!
ERR! npm ERR! A complete log of this run can be found in:
ERR! npm ERR!     C:\Users\*****\AppData\Local\npm-cache\_logs\2023-04-18T06_12_52_428Z-debug-0.log
ERR!
ERR!     at NPMProxy.executeCommand (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\cli\dist\generate.js:39:1669)
ERR!     at NPMProxy.findInstallations (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\cli\dist\generate.js:39:2303)
ERR!     at automigrate (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\cli\dist\generate.js:317:1066)
ERR!     at async doUpgrade (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\cli\dist\generate.js:390:2893)
ERR!     at async withTelemetry (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\core-server\dist\index.js:35:3422)
ERR!     at async upgrade (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\cli\dist\generate.js:390:3336)
ERR!  Error: npm ERR! code ELSPROBLEMS
ERR! npm ERR! invalid: typescript@5.0.3 C:\Users\*****\Projects\*****\**********\node_modules\typescript
ERR! npm ERR! invalid: acorn@7.4.1 C:\Users\*****\Projects\*****\**********\node_modules\acorn
ERR! npm ERR! invalid: glob@7.2.3 C:\Users\*****\Projects\*****\**********\node_modules\glob
ERR! npm ERR! invalid: ajv@6.12.6 C:\Users\*****\Projects\*****\**********\node_modules\ajv
ERR! npm ERR! invalid: rollup@3.20.2 C:\Users\*****\Projects\*****\**********\node_modules\rollup
ERR! {
ERR!   "error": {
ERR!     "code": "ELSPROBLEMS",
ERR!     "summary": "invalid: typescript@5.0.3 C:\\Users\\*****\\Projects\\*****\\**********\\node_modules\\typescript\r\ninvalid: acorn@7.4.1 C:\\Users\\*****\\Projects\\*****\\**********\\node_modules\\acorn\r\ninvalid: glob@7.2.3 C
:\\Users\\*****\\Projects\\*****\\**********\\node_modules\\glob\r\ninvalid: ajv@6.12.6 C:\\Users\\*****\\Projects\\*****\\**********\\node_modules\\ajv\r\ninvalid: rollup@3.20.2 C:\\Users\\*****\\Projects\\*****\\**********\\node_modules\\rollup",
ERR!     "detail": ""
ERR!   }
ERR! }
ERR!
ERR! npm ERR! A complete log of this run can be found in:
ERR! npm ERR!     C:\Users\*****\AppData\Local\npm-cache\_logs\2023-04-18T06_12_52_428Z-debug-0.log
ERR!
ERR!     at NPMProxy.executeCommand (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\cli\dist\generate.js:39:1669)
ERR!     at NPMProxy.findInstallations (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\cli\dist\generate.js:39:2303)
ERR!     at automigrate (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\cli\dist\generate.js:317:1066)
ERR!     at async doUpgrade (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\cli\dist\generate.js:390:2893)
ERR!     at async withTelemetry (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\core-server\dist\index.js:35:3422)
ERR!     at async upgrade (C:\Users\*****\Projects\*****\**********\node_modules\@storybook\cli\dist\generate.js:390:3336)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@valentinpalkovic valentinpalkovic

Labels
bug cli
Projects
Core Team Projects
Archived in project
Milestone
No milestone