no such file or directory, rename ***

[lius123]

• Electron-Builder Version:
  22.5.1

• Node Version:
  14.17.3

• Electron Version: 13.1.7
• Electron Type (current, beta, nightly):

• Target:
  windows

I encountered a problem when packing:

The bundle size is significantly larger than recommended.
Consider reducing it with code splitting: https://umijs.org/docs/load-on-demand
You can also analyze the project dependencies using ANALYZE=1

• electron-builder version=22.11.7 os=10.0.19042
• loaded configuration file=package.json ("build" field)
• writing effective config file=release\0.0.1_setup\builder-effective-config.yaml
• rebuilding native dependencies dependencies=node-sass@4.14.1 platform=win32 arch=x64
• packaging platform=win32 arch=x64 electron=13.1.7 appOutDir=release\0.0.1_setup\win-unpacked
⨯ ENOENT: no such file or directory, rename 'D:\moushi\im-pc\release\0.0.1_setup\win-unpacked\electron.exe' -> 'D:\moushi\im-pc\release\0.0.1_setup\win-unpacked\APP.exe' failedTask=build stackTrace=Error: ENOENT: no such file or directory, rename 'D:\moushi\im-pc\release\0.0.1_setup\win-unpacked\electron.exe' -> 'D:\moushi\im-pc\release\0.0.1_setup\win-unpacked\APP.exe'

my build config

"build": {
"extends": null,
"productName": "APP",
"appId": "com.moushi.app",
"directories": {
"output": "release/${version}_setup"
},
"files": [
"!node_modules//*",
"src/main//",
"src/main/public",
"src/render/dist/**/"
],
"mac": {
"target": [
"dmg",
"zip"
]
},
"win": {
"target": [
{
"target": "nsis",
"arch": [
"x64",
"ia32"
]
}
],
"artifactName": "${productName}setup${version}.${ext}",
"icon": "src/main/public/icon.ico"
},
"publish": [
{
"provider": "generic",
"url": ""
}
],
"nsis": {
"oneClick": false,
"perMachine": false,
"allowToChangeInstallationDirectory": true,
"deleteAppDataOnUninstall": false
}
},

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[anlate]

i meet the same problem, do u resolved this?

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[einarchive]

Same error is happening to me, did any of you find a workaround by any chance?

[1yasa]

+1