2021-01-14
1518
#electron#react
Felix Rieseberg
32073
Jan 14, 2021 ⋅ 5 min read

Electron-forge vs. electron-react-boilerplate

Felix Rieseberg Desktop apps at Slack, co-maintainer of Electron.js, teacher and speaker on JS Stunts, and a triathlete.

Recent posts:

DesignCoder and the future of AI-generated UI

From sketches to code in minutes, DesignCoder shows how AI-generated, hierarchy-aware UIs could change the way developers prototype and ship apps.

Rosario De Chiara
Oct 7, 2025 ⋅ 5 min read

Would You Use If() functions in CSS?

It’s 2025, and CSS finally thinks logically. The if() function brings real conditional styling — no hacks, no JS workarounds. Here’s how to use it right.

Ikeh Akinyemi
Oct 7, 2025 ⋅ 16 min read
Typescript or Zod for Validation?

TypeScript vs Zod: Clearing up validation confusion

Learn when to use TypeScript, Zod, or both for data validation. Avoid redundant checks and build safer, type-sound applications.

Alexander Godwin
Oct 6, 2025 ⋅ 3 min read
Wasm 3 Before GTA 6 LogRocket Article

We got Wasm 3.0 before GTA 6: Meet the web’s new engine

Discover how WebAssembly 3.0’s garbage collector, exception handling, and Memory64 transform Wasm into a true mainstream web platform.

Ikeh Akinyemi
Oct 3, 2025 ⋅ 2 min read
View all posts

3 Replies to "Electron-forge vs. electron-react-boilerplate"

  1. One star. It’d be nice if you actually showed how to add React to electron-forge! Adding the react dependencies is not the same as adding the scaffolding and start up code for a react project!

  2. and yet, nothing works out of the box, always need downgrading and sorting packageJSON, and that’s when you follow formal documentation. not very beginner friendly

Leave a Reply