storybookjs/storybook

[Bug]: automigrate fails on EXDEV error

Open

#30,184 opened on 2025年1月3日

GitHub で見る
 (5 comments) (2 reactions) (0 assignees)TypeScript (89,909 stars) (10,058 forks)batch import
automigrationsbughelp wantedwindows

説明

Describe the bug

Running the command automigrate on windows, it tries to move the logfile from user's temp folder to the current project folder by renaming it. This fails, if temp folder and project folder are on different drives/partitions with the error: Error: EXDEV: cross-device link not permitted, rename 'C:\Users\[USER]\AppData\Local\Temp\435cc8918d4e493a2eb400fc4351782f\migration-storybook.log' -> '.\migration-storybook.log'

Reproduction link

NONE

Reproduction steps

No response

System

Storybook Environment Info:

  System:
    OS: Windows 11 10.0.22631
    CPU: (16) x64 AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics
  Binaries:
    Node: 22.12.0 - C:\Program Files\nodejs\node.EXE
    npm: 11.0.0 - ~\AppData\Roaming\npm\npm.CMD <----- active
  Browsers:
    Edge: Chromium (128.0.2739.79)
  npmPackages:
    @storybook/addon-a11y: ^8.4.7 => 8.4.6
    @storybook/addon-coverage: ^1.0.4 => 1.0.4
    @storybook/addon-docs: ^8.4.7 => 8.4.6
    @storybook/addon-essentials: ^8.4.7 => 8.4.6
    @storybook/addon-interactions: ^8.4.7 => 8.4.6
    @storybook/addon-jest: ^8.4.7 => 8.4.6
    @storybook/addon-links: ^8.4.7 => 8.4.6
    @storybook/angular: ^8.4.7 => 8.4.6
    @storybook/core-server: ^8.4.7 => 8.4.6
    @storybook/test-runner: 0.19.0 => 0.19.0
    storybook: ^8.4.7 => 8.2.8
  npmGlobalPackages:
    @storybook/cli: 8.4.7

Additional context

No response

コントリビューターガイド