Skip to content

Commit

Permalink
eof newline
Browse files Browse the repository at this point in the history
  • Loading branch information
erickzhao committed Jul 17, 2024
1 parent eff91ed commit b285b1c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion core-concepts/why-electron-forge.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,4 +33,4 @@ The key difference in philosophy between the two projects is that Electron Forge
We believe there are two main advantages to using Forge:

1. **Forge receives new features for application building as soon as they are supported in Electron** (e.g. [ASAR integrity](https://electronjs.org/docs/latest/tutorial/asar-integrity) or [universal macOS builds](https://github.com/electron/universal)). These features are built with first-party Electron tooling in mind, so Forge receives them as soon as they are released.
2. **Forge's multi-package architecture makes it easier to understand and extend.** Since Forge is made up of many smaller packages with clear responsibilities, it is easier to follow the flow of the code. Also, its extensible API design means that you can write your own build logic separate from the provided configuration options for advanced use cases.
2. **Forge's multi-package architecture makes it easier to understand and extend.** Since Forge is made up of many smaller packages with clear responsibilities, it is easier to follow the flow of the code. Also, its extensible API design means that you can write your own build logic separate from the provided configuration options for advanced use cases.

0 comments on commit b285b1c

Please sign in to comment.