Getting caught up with Electron

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
electron
Domain
build-system, desktop

Research direction

Start with the existing electron-packager command in the issue and review the current Electron and build-tool release documentation it references. Determine the required changes to bring the macOS build process up to date, then verify that the app still builds and that its file dialogs work as expected.

Written by the indexing model from the issue text.

Description

A query for Electron devs.

I have been developing Electron apps for five years at least.

I have an Electron version of "Drummer" for the Mac (to start) almost ready to go, but there are problems with the File dialogs. It feels like a versioning thing? These routines worked fine in earlier software. So I figure what I need to do is get this app building using the latest versions of Electron and the latest build tools. If I recall correctly they change a lot. And it's been a while since I figured out how to do it. When I read their docs for building stuff I feel as lost as I felt when I was just starting out.

Okay, so here's how I build the app currently:

sudo electron-packager . "Electric Drummer" --platform=darwin --arch=all --overwrite --icon=drummer.icns --electron-version=7.1.10

What should I change to get my build process up to date?

It works, it builds the app, and I've been using it, it's just not the current Electron release and their are quirks with the file dialogs.

Ideally I'd like to not have to learn too much about the the Electron release process or versions -- just give me something that works and I can get back to my sprawling codebase.

Thanks in advance. 😄

Dominant language
HTML
Stars
134
Forks
10
No merged PRs in 30d

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 scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.