关于盖茨比的EBUSY

Question

当运行'gatsby develop‘或'gatsby build’时，会返回此错误，导致构建失败。

ordpress/05131cb1d9a46f72f621b56852b5ab9a/rs-hero.png to C:\__PATH__\public\static\d7c151e623bf472c2f10e2ce051fe8d8\rs-hero.png [Error: EBUSY: resource busy or locked,
copyfile 'C:\__PATH__\.cache\caches\gatsby-source-wordpress\05131
cb1d9a46f72f621b56852b5ab9a\rs-hero.png' -> 'C:\__PATH__\public\s
tatic\d7c151e623bf472c2f10e2ce051fe8d8\rs-hero.png'] {
  errno: -4082,
  code: 'EBUSY',
  syscall: 'copyfile',
  path: 'C:\\__PATH__\\.cache\\caches\\gatsby-source-wordpress\\05131cb1d9a46f72f621b56852b5ab9a\\rs-hero.png',
  dest: 'C:\\__PATH__\\public\\static\\d7c151e623bf472c2f10e2ce
051fe8d8\\rs-hero.png'
}

这是我的gatsby信息：

    OS: Windows 10 10.0.19042
    CPU: (16) x64 Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Binaries:
    Node: 14.15.4 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.15 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.10 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (95.0.1020.30)
  npmPackages:
    gatsby: ^4.0.1 => 4.0.1
    gatsby-background-image: ^1.5.3 => 1.5.3
    gatsby-plugin-feed: ^4.0.0 => 4.0.0
    gatsby-plugin-google-tagmanager: ^4.0.0 => 4.0.0
    gatsby-plugin-image: ^2.0.0 => 2.0.0
    gatsby-plugin-manifest: ^4.0.0 => 4.0.0
    gatsby-plugin-nprogress: ^4.0.0 => 4.0.0
    gatsby-plugin-offline: ^5.0.0 => 5.0.0
    gatsby-plugin-react-helmet: ^5.0.0 => 5.0.0
    gatsby-plugin-react-svg: ^3.0.1 => 3.1.0
    gatsby-plugin-remove-fingerprints: ^0.0.2 => 0.0.2
    gatsby-plugin-sass: ^5.0.0 => 5.0.0
    gatsby-plugin-sharp: ^4.0.1 => 4.0.1
    gatsby-plugin-sitemap: ^4.10.0 => 4.10.0
    gatsby-plugin-styled-components: ^4.14.0 => 4.14.0
    gatsby-plugin-svgr-loader: ^0.1.0 => 0.1.0
    gatsby-plugin-web-font-loader: ^1.0.4 => 1.0.4
    gatsby-source-filesystem: ^4.0.0 => 4.0.0
    gatsby-source-wordpress: ^6.0.0 => 6.0.0
    gatsby-transformer-sharp: ^4.0.0 => 4.0.0
  npmGlobalPackages:
    gatsby-cli: 4.0.0

我尝试过清除npm缓存和gatsby缓存。似乎什么都不起作用。

Answer 1

尝试删除所有node_modules并重新安装它们，而不是清除缓存(并保留文件)：

删除删除和package-lock.json

• Run npm install

• Run npm cache clean (可能不需要此步骤)