You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building the project with target win as portable and then trying to run it, the following error message is appearing.
There are no errors during building the application. cannot find module '@socket.io/component-emitter'
After inspecting the created app.asar archive, the package is included.
When running electronize start, then the app is starting without problems.
This is related to the issue electron-userland/electron-builder#8244 . I don't know the exact problem of the new electron-builder, but when switching back to version 24.13.3 of the electron-builder the application can start after building.
Intermediate solution:
Set electron-builder version to 24.13.3 locally
npm install -g electron-builder@24.13.3
npm link electron-builder
ElectronNET.CLI Version: 23.6.2.0
.Net 6
Node.JS v18.18.2
electronize build /target win
When building the project with target win as portable and then trying to run it, the following error message is appearing.
There are no errors during building the application.
cannot find module '@socket.io/component-emitter'
After inspecting the created app.asar archive, the package is included.
When running
electronize start
, then the app is starting without problems.Steps to Reproduce:
electronize build /target win
cannot find module '@socket.io/component-emitter'
appearsReason:
This is related to the issue electron-userland/electron-builder#8244 . I don't know the exact problem of the new electron-builder, but when switching back to version 24.13.3 of the electron-builder the application can start after building.
Intermediate solution:
Set electron-builder version to 24.13.3 locally
Proposed solution
Set a fixed version of electron-builder in the https://github.com/ElectronNET/Electron.NET/blob/main/src/ElectronNET.CLI/Commands/BuildCommand.cs#L201 to avoid unexpected behaviour in the future.
The text was updated successfully, but these errors were encountered: