-
Notifications
You must be signed in to change notification settings - Fork 21
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.
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
Studio: Update electron-forge to the latest version 7.6.0 #795
Studio: Update electron-forge to the latest version 7.6.0 #795
Conversation
7c94f89
to
e53605c
Compare
@@ -55,6 +55,7 @@ const config: ForgeConfig = { | |||
? [] | |||
: [ | |||
new MakerDMG( | |||
// @ts-expect-error - https://github.com/electron/forge/issues/3712 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is bug in the MakerDMG - appPath
is required by mistake, and it should be optional in the next release. So we will remove this @ts-expect-error
when it's fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bug is closed. Does it mean it was not released yet?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The suggested approach looks great, thanks for linking to the issue in Electron repository.
The app builds and starts on my local without issues.
@@ -55,6 +55,7 @@ const config: ForgeConfig = { | |||
? [] | |||
: [ | |||
new MakerDMG( | |||
// @ts-expect-error - https://github.com/electron/forge/issues/3712 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bug is closed. Does it mean it was not released yet?
Related issues
Proposed Changes
Here we reverted electron-forge to 7.3.1, but the actual issue was connected not to electron-forge, it was about
@electron/packager
, which we pinned to18.1.3
version. So actually, there is no sense to keep pinned both -electron-forge
and@electron/packager
. As a result, since@electron/packager
is anyway has pinned version, then we are safe to continue updatingelectron-forge
to new versions, as long as it works well.With this PR I propose to update electron-forge to the latest version and create a new issue to remove overrides for "@electron/packager": "18.1.3", when the package is fixed.
In the history of commits of this PR you can see that if we unpin override for @electron/packager then it has still the old error. And actually the open issue confirms that the issue still exists.
And I tested - the latest electron-forge works well.
Testing Instructions
npm start
)npm run make
./out
directoryWindows Dev Build
)