2020-10-21 03:21:38 +03:00
|
|
|
# @electron/universal
|
|
|
|
|
|
|
|
|
|
> Create universal macOS Electron applicatiojns
|
|
|
|
|
|
|
|
|
|
[](https://circleci.com/gh/electron/universal)
|
|
|
|
|
|
2020-10-27 01:33:06 +03:00
|
|
|
|
2020-10-21 03:21:38 +03:00
|
|
|
## Usage
|
|
|
|
|
|
|
|
|
|
```typescript
|
|
|
|
|
import { makeUniversalApp } from '@electron/universal';
|
2020-10-27 01:33:06 +03:00
|
|
|
|
|
|
|
|
await makeUniversalApp({
|
|
|
|
|
x64AppPath: 'path/to/App_x64.app',
|
|
|
|
|
arm64AppPath: 'path/to/App_arm64.app',
|
|
|
|
|
outAppPath: 'path/to/App_universal.app',
|
|
|
|
|
});
|
2020-10-21 03:21:38 +03:00
|
|
|
```
|
2020-11-14 00:13:39 +03:00
|
|
|
|
|
|
|
|
## 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.
|
