From b285b1c1084fff8b101b4568bf65c2712e86f20a Mon Sep 17 00:00:00 2001 From: Erick Zhao Date: Wed, 17 Jul 2024 11:59:22 -0700 Subject: [PATCH] eof newline --- core-concepts/why-electron-forge.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core-concepts/why-electron-forge.md b/core-concepts/why-electron-forge.md index d5ff77a..59c42b6 100644 --- a/core-concepts/why-electron-forge.md +++ b/core-concepts/why-electron-forge.md @@ -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. \ No newline at end of file +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.