Getting caught up with Electron
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Refactorización
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- electron
- Área
- build-system, desktop
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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. 😄
- Lenguaje dominante
- HTML
- Estrellas
- 134
- Forks
- 10
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de scripting/Scripting-News
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
scripting/Scripting-News#353 · 6 comentarios ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 75/100
scripting/Scripting-News#332 · 25 comentarios · 1 reacción ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
scripting/Scripting-News#362 ·
-
Matt is moved aside Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
scripting/Scripting-News#361 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
scripting/Scripting-News#360 · 1 comentario · 1 reacción ·
Todos los issues de scripting/Scripting-News
Issues similares
-
Name consistency Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
eellak/triplestore#65 · 1 comentario ·
-
litertlm-android AAR ships no consumer ProGuard rules → "mid == null" SIGABRT in minified apps Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
google-ai-edge/LiteRT-LM#3739 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
area-Bzlmod team-ExternalDeps type: bug untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
bazelbuild/bazel#31291 · 2 comentarios ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
bradcypert/plum#53 ·