Skip to content
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.

Sign up for GitHub

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

chore: Forge v6 blog post #278

Merged
merged 16 commits into from
Nov 3, 2022
Merged

chore: Forge v6 blog post #278

Changes from 1 commit
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
b5ba893
chore: Forge v6 blog post
georgexu99 Oct 13, 2022
300ac33
chore: update stable release section and add switching section
georgexu99 Oct 13, 2022
4f24469
minor change
georgexu99 Oct 13, 2022
d708384
change breaking changes to breaking changes since beta
georgexu99 Oct 13, 2022
ae2d5ce
add switching para
georgexu99 Oct 17, 2022
61c7ff1
sentence case for headers
georgexu99 Oct 18, 2022
f0c47d2
re-add migration section
georgexu99 Oct 24, 2022
fc894c6
update breaking changes
georgexu99 Oct 24, 2022
ce54770
beef up call to action
georgexu99 Oct 31, 2022
4f8a4f0
resolve comments
georgexu99 Oct 31, 2022
8fce9e4
another round of edits
georgexu99 Nov 1, 2022
5a7bb5e
add init section
georgexu99 Nov 1, 2022
73c451d
docs: move identityValidation rename to be logically cohesive with os…
georgexu99 Nov 2, 2022
9efdbcd
reformat breaking changes
georgexu99 Nov 2, 2022
01665d1
remove dead links
georgexu99 Nov 2, 2022
267553b
final pass
erickzhao Nov 3, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 12 additions & 5 deletions blog/forge-v6-release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,9 @@ authors:
- name: vertedinde
url: 'https://github.com/vertedinde'
image_url: 'https://github.com/vertedinde.png?size=96'
- name: erickzhao
url: 'https://github.com/erickzhao'
image_url: 'https://github.com/erickzhao.png?size=96'
slug: forge-v6-release-blog
georgexu99 marked this conversation as resolved.
Show resolved Hide resolved
---

Expand All @@ -23,7 +26,9 @@ A stable release means that we are done making major breaking changes, and that

If your app already uses an existing build tooling solution that provides packaging and publishing capabilities, the benefits associated with adopting Electron Forge can still outweigh the initial switching cost.
erickzhao marked this conversation as resolved.
Show resolved Hide resolved

Electron Forge will be kept up to date with the latest Electron tooling updates. This means that alongside the implicit features and plugins that Forge provides, users won't need to wire in new tooling support themselves, or wait for that support to be eventually implemented by other packages before upgrading. This reduction in the burden of maintenance for Forge applications has already been observed when Electron released `@electron/universal` [support](https://github.com/electron/universal) as well as [ASAR Integrity checking](https://www.electronjs.org/docs/latest/tutorial/asar-integrity), which were features that Forge supported out of the box.
Electron Forge will receive features from the latest Electron tooling updates as soon as they come out. This means that alongside the implicit features and plugins that Forge provides, users won't need to wire in new tooling support themselves, or wait for that support to be eventually implemented by other packages before upgrading. This reduction in the burden of maintenance for Forge applications has already been observed when Electron released `@electron/universal` [support](https://github.com/electron/universal) as well as [ASAR Integrity checking](https://www.electronjs.org/docs/latest/tutorial/asar-integrity), which were features that Forge supported out of the box.

In addition, Forge was built with the intention of supporting custom plugins, makers and publishers. Forge's extensible API design means that you can write your own additional build logic for any advanced use cases that you may require. For more details, see the [Extending Electron Forge] section of the docs.

## Introducing the Webpack Plugin

Expand Down Expand Up @@ -52,11 +57,13 @@ _A complete list of changes and commits can be found [here](https://github.com/e
- renamed the default repository branch from `master` to `main` ([#2946](https://github.com/electron-userland/electron-forge/commit/d28974e35b5e64aa94e6cc53dce36c8e53f5b5bf))
- renamed `electronRebuildConfig` to `rebuildConfig` ([placeholdercommitmsg](https://github.com/electron-userland/electron-forge/pull/2963))
- renamed `identity-validation` to`identityValidation` ([#2959](https://github.com/electron-userland/electron-forge/commit/dba9359026b6b72479bff8133ec0c2c2e05d5595))

## A Call to Action:
georgexu99 marked this conversation as resolved.
Show resolved Hide resolved
Tell us what you need! The Electron Forge Team is always looking to build the project to better suit its users. You can help us improve Electron Forge by submitting feature requests, posting issues, or just letting us know your feedback!

<!-- links -->

[Core API]: https://www.npmjs.com/package/@electron-forge/core
[CLI API]: https://www.npmjs.com/package/@electron-forge/cli
[webpack template]: https://www.electronforge.io/templates/webpack-template



[webpack template]: https://www.electronforge.io/templates/webpack-template]
[Extending Electron Forge]: https://www.electronforge.io/advanced/extending-electron-forge