Create Universal macOS applications from two x64 and arm64 Electron applications
Перейти к файлу
Samuel Attard 479e80d6a9
fix: handle MainMenu.nib mismatch in Electron 18 (#42)
2022-03-09 11:04:13 -08:00
.circleci build: move to support CFA branch naming 2020-11-13 14:01:49 -08:00
entry-asar fix: no asar support (#4), renamed directories (#5) and check if we need to duplicate asar's (#2) (#8) 2020-11-19 09:34:14 -08:00
src fix: handle MainMenu.nib mismatch in Electron 18 (#42) 2022-03-09 11:04:13 -08:00
.gitignore Initial Commit 2020-10-21 13:30:28 -07:00
.prettierrc.json Initial Commit 2020-10-21 13:30:28 -07:00
.releaserc.json build: move to support CFA branch naming 2020-11-13 14:01:49 -08:00
README.md docs: update CircleCI readme badge 2020-11-26 13:42:27 -08:00
package.json feat: add option to merge ASARs (#34) 2022-01-25 10:35:57 +13:00
tsconfig.esm.json Initial Commit 2020-10-21 13:30:28 -07:00
tsconfig.json Initial Commit 2020-10-21 13:30:28 -07:00
yarn.lock build(deps): bump node-fetch from 2.6.1 to 2.6.7 (#38) 2022-02-03 11:50:56 -08:00

README.md

@electron/universal

Create universal macOS Electron applications

CircleCI

Usage

import { makeUniversalApp } from '@electron/universal';

await makeUniversalApp({
  x64AppPath: 'path/to/App_x64.app',
  arm64AppPath: 'path/to/App_arm64.app',
  outAppPath: 'path/to/App_universal.app',
});

FAQ

The app is twice as big now, why?

Well, a Universal app isn't anything magical. It is literally the x64 app and the arm64 app glued together into a single application. It's twice as big because it contains two apps in one.

What about native modules?

The way @electron/universal works today means you don't need to worry about things like building universal versions of your native modules. As long as your x64 and arm64 apps work in isolation the Universal app will work as well.

How do I build my app for Apple silicon in the first place?

Check out the Electron Apple silicon blog post