Create Universal macOS applications from two x64 and arm64 Electron applications

Перейти к файлу

Samuel Attard 64cbc83faf build: configure semantic release for main branch		2022-10-18 16:08:05 -07:00
.circleci	build: configure semantic release for main branch	2022-10-18 16:08:05 -07: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: migrate from asar to @electron/asar	2022-10-18 16:06:38 -07: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: configure semantic release for main branch	2022-10-18 16:08:05 -07:00
README.md	build: migrate master <-> main	2022-10-18 16:05:13 -07:00
package.json	fix: migrate from asar to @electron/asar	2022-10-18 16:06:38 -07: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	fix: migrate from asar to @electron/asar	2022-10-18 16:06:38 -07:00

README.md

@electron/universal

Create universal macOS Electron applications

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