Develop cross-platform desktop applications with Electron on Windows on Arm
Introduction
Create the application using the electron framework
Build the cross-platform application
Next Steps
Develop cross-platform desktop applications with Electron on Windows on Arm
Who is this for?
This Learning Path is for developers who want to learn how to develop cross-platform desktop applications using the Electron Framework on Windows on Arm (WoA).
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Implement a sample application using the electron framework on a Windows on Arm machine
- Learn how to create a multi platform build of the application
Prerequisites
Before starting, you will need the following:
- A Windows on Arm computer such as the Lenovo Thinkpad X13s running Windows 11 or a Windows on Arm virtual machine .
- Node.js for Arm64. You can find the Node.js installer .
- Any code editor; we recommend using Visual Studio Code for Arm64 .
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
npm, update package.json, and target Arm64 and x64 from one codebase. You’ll build both Arm64 and x64 variants, inspect console output, and identify where to change future packaging settings.Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
devDependencies.package.json changes.package.json file in your project folder. Add or update the Electron Builder configuration so it includes both Arm64 and x64 targets.package.json, run your build and check that artifacts are generated for both Arm64 and x64. If only one appears, review the targets configured in package.json.npm audit. To complete the Learning Path, continue with configuration and application builds.