Feature request: support non-mac development platform

Open
#144 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
electron, macos, typescript

Research direction

The issue does not name any files, tests, or entry points. Start by locating the platform-specific build logic for this package and determine which limitation requires macOS; done means producing universal packages from non-macOS development platforms without breaking existing x64 and arm64 use cases.

Written by the indexing model from the issue text.

Description

Creating a universal package is useful, but this package requires the user to be on a mac development environment to use it. This doesn't seem like it should be necessary. Requiring a mac build environment creates friction for using this tool.

Suggestion: Make this package work regardless of the development platform. I don't know how feasible this is as I am not sure what technical limitation is currently making it platform-specific.

For context, we have a game on Steam which we release Windows / Linux / Mac versions for. We have been releasing a darwin-x64 package, but we have users reporting slowness on modern macs. If we switch the mac packages to arm64, then it would be a compatibility break for users on older x64 Mac machines, so we were considering using universal packages, but the requirement of using a mac build platform is making it more difficult than it ought to be to make a universal package, and we will probably have to go with a different, less elegant solution.

Dominant language
TypeScript
Stars
148
Forks
48
Avg merge
3h 57m
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from electron/universal

All issues in electron/universal

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.