Electron está actualmente en pausa con los lanzamientos principales

¿Qué está pasando?​

Nuestro Calendario de lanzamiento principal se mueve a la par de Chromium y el proyecto Chromium ha tomado la reciente decisión pausar sus lanzamientos debido a los horarios de trabajo ajustados. Esto significa que durante la duración de la cadencia alterada de Chromium, Electron también pausará temporalmente nuevas versiones importantes.

Creemos que nuestra mejor opción es seguir los pasos de Chromium, y por eso mientras tanto el equipo de Electron cambiará a trabajo de tiempo completo en resolver errores, seguridad, performance y estabilidad.

Queremos asegurarnos de que tanto el bienestar de nuestros mantenedores como el de nuestros consumidores sea prioritario durante este tiempo, por lo que agradecemos sus comentarios y esperamos volver a nuestro programa de lanzamiento regular.

Para más actualizaciones, por favor sigue nuestra Cuentea de Twitter.

Edición (2020-03-30): Electron 9 estable apuntará a Chromium M83 y será lanzado el 19 de mayo de 2020, en respuesta al anuncio de Chromium de omitir la fecha estable de M82 y ajustar la fecha estable de M83.

At Node+JS Interactive in Montreal, the OpenJS Foundation announced that it accepted Electron into the Foundation's incubation program. The Foundation is committed to supporting the healthy growth of the JavaScript ecosystem and web technologies by providing a neutral organization to host and sustain projects, as well as collaboratively fund activities for the benefit of the community at large.

The OpenJS Foundation is host to a number of open source JavaScript projects including jQuery, Node.js, and webpack. It's supported by 30 corporate and end-user members, including GoDaddy, Google, IBM, Intel, Joyent, and Microsoft. Electron is an open–source framework for building cross-platform desktop applications with web technologies.

This is an exciting move for Electron, and we see it as a next step in our evolution as an open-source project.

What this means for developers​

Electron joining the OpenJS Foundation does not change how Electron is made, released, or used — and does not directly affect developers building applications with Electron. Even though Electron was originally created at GitHub in 2013, it is currently maintained by a number of organizations and individuals. In 2019, Electron codified its governance structure and invested heavily into formalizing how decisions affecting the entire project are made. We believe that having multiple organizations and developers investing in and collaborating on Electron makes the project stronger.

Lifting Electron up from being owned by a single corporate entity and moving it into a neutral foundation focused on supporting the web and JavaScript ecosystem is a natural next step as we mature as an open-source project.

Learning more​

You can read up on the foundation, its mission, and its members on the OpenJSF website. For more information and quotes about the acceptance of Electron into the OpenJSF incubation program, check out the official press release. To learn more about the humans behind Electron and how they work together, take a look at our Governance page.

To get started with Electron itself, take a peek at our documentation.

🎉 ¡Electron se está trabajando para lanzar una nueva versión estable cada 12 semanas! 🎉

⚡️ ¡Guau eso es rápido! Pero ¿por qué?​

En pocas palabras, Chromium no detiene el lanzamiento por lo que Electron tampoco va a desacelerar.

Chromium lanza una version programada cada 6 semanas. Para entregar las versiones más actualizadas de Chromium en Electron, nuestro programa necesita seguir el suyo. Puede encontrar más información sobre el ciclo de lanzamiento de Chromium aquí.

🚀 ¿Por qué cada 12 semanas?​

Cada 6 semanas, una nueva versión de Chromium viene con nuevas características, correcciones de errores / correcciones de seguridad y mejoras de V8. Los usuarios de Electron han sido fuerte y claros acerca de querer estos cambios de una manera oportuna, así que hemos ajustados nuestra fechas de lanzamientos estables para coincidir con los lanzamientos estables de Chromium. Primero, Electron v6.0.0 incluirá M76 y la fecha de publicación de la versión estable es 30 de Julio 30, 2019, el mismo día de lanzamiento que Chromium M76.

🚧 Qué significa esto para mi y mi aplicación Electron?​

Tendrás acceso a nuevas características y correcciones de Chromium y V8 más temprano que antes. Importantemente, además sabrás cuando se acercan esos cambios, así que serás capaz de planificar con mejor información que antes.

El equipo de Electron continuará soportando las últimas tres versiones mayores. Por ejemplo, cuando v6.0.0 sea estable el 30 de Julio, 2019, soportaremos v6.x, v5.x, y v4.x, mientras que la v3.x alcanzará el final de su vida.

💬 Programa de retroalimentación​

Por favor considere unirse a nuestro Programa de comentarios sobre la aplicación para ayudarnos con nuestros lanzamientos beta y estabilizaciones. Projects who participate in this program test Electron betas on their apps; and in return, the new bugs they find are prioritized for the stable release.

📝 Una breve historia de los lanzamientos de Electron​

Las decisiones acerca de las versiones estables antes de la v3.0.0 no seguían un agenda. Añadimos programas internos al proyecto con v3.0.0 y v4.0.0. A principios de este año, decidimos publicar nuestra fecha de lanzamiento estable por primera vez para Electron v5.0.0. Anunciar fechas de lanzamiento estables fue recibido positivamente en general y estamos encantados de seguir haciéndolo para futuras versiones.

Para optimizar mejor estos esfuerzos relacionados con la actualización, nuestros grupos de trabajos Upgrades y Releases fueron creados dentro de nuestro Governance. Ellos nos han permitido priorizar y delegar mejor este trabajo, el cual esperamos que se haga más evidente con la lanzamiento posterior.

Aquí es donde nuestra nueva cadencia nos colocará en comparación con la cadencia de Chromium:

📨 Si tienes alguna pregunta, por favor envíanos un correo electrónico a info@electronjs.org.

As Electron grows in popularity for desktop applications, the team working on it has also grown: we have more fulltime maintainers who work for different companies, live in different timezones, and have different interests. We're introducing a governance structure so we can keep growing smoothly.

Why are things changing?​

People in the Electron project coordinate in timezones around the world with volunteers, with full-time maintainers, and with several companies who all rely on Electron. Until now, we've been successful with informal coordination; but as the team has grown, we've found that the approach doesn't scale. We also want to make it easier for new contributors to find a place to call home in the project.

Grupos de trabajo​

Electron governance includes working groups that are responsible for different parts of the project. We're starting out with seven groups:

• Community & Safety: Handles Code of Conduct issues.
• Docs & Tooling: Oversees externally-focused tooling (e.g. Fiddle, Forge) and the Electron documentation.
• Outreach: Helps grow the Electron community.
• Releases: Ensures releases are stable and on schedule.
• Security: Performs security testing and responds to security issues.
• Upgrades: Integrates upstream upgrades, such as new versions of V8, Chromium, and Node.
• Website: Maintains and improves the Electron website.

These groups will coordinate with each other, but each has their own meeting schedules and agendas to be productive on their own. More details on these groups are available at the governance repository.

Does this change the Electron project's direction?​

This shouldn't have any direct effect on Electron's direction. If our strategy is successful, working groups will make it easier for new contributors to find topics that interest them, and make maintainers' lives simpler by moving discussion unrelated to their day-to-day work to other groups. If that happens, it may indirectly affect things by having more unblocked people working together.

Where can I learn more?​

• The governance repo and charter have information about the new governance structure.
• Each working group has its own page: Community, Docs & Tools, Outreach, Releases, Security, Upgrades, and Website.
• You can contact the maintainers by opening an issue or mailing us at info@electronjs.org.

El equipo de Electron suspenderá el soporte para Linux de 32 bits (ia32 / i386) a partir de Electron v4.0. La última versión de Electron que soporta instalaciones basadas en 32 bits de Linux es Electron v3.1, que recibirá versiones de soporte hasta que Electron v6 sea liberado. Support for 64-bit based Linux and armv7l will continue unchanged.

What exactly is Electron no longer supporting?​

You may have seen the description "64-bit" and "32-bit" as stickers on your computer or as options for downloading software. The term is used to describe a specific computer architecture. Most computers made in the 1990s and early 2000s were made with CPUs that were based on the 32-bit architecture, while most computers made later were based on the newer and more powerful 64-bit architecture. The Nintendo 64 (get it?) and the PlayStation 2 were the first widely available consumer devices with the new architecture, computers sold after 2010 contained almost exclusively 64-bit processors. As a result, support has been shrinking: Google stopped releasing Chrome for 32-bit Linux in March 2016, Canonical stopped providing 32-bit desktop images in 2017 and dropped support for 32-bit altogether with Ubuntu 18.10. Arch Linux, elementary OS, and other prominent Linux distributions have already dropped support for the aging processor architecture.

Until now, Electron has provided and supported builds that run on the older 32-bit architecture. From release v4.0 onwards, the Electron team will no longer be able to provide binaries or support for 32-bit Linux.

Electron has always been a vibrant open source project and we continue to support and encourage developers interested in building Electron for exotic architectures.

What does that mean for developers?​

If you are not currently providing 32-bit distributions of your app for Linux, no action is required.

Projects which ship 32-bit Linux Electron applications will need to decide how to proceed. 32-bit Linux will be supported on Electron 3 until the release of Electron 6, which gives some time to make decisions and plans.

What does that mean for users?​

If you are a Linux user and not sure whether or not you're running a 64-bit based system, you are likely running on a 64-bit based architecture. To make sure, you can run the lscpu or uname -m commands in your terminal. Either one will print your current architecture.

If you are using Linux on a 32-bit processor, you have likely already encountered difficulties finding recently released software for your operating system. The Electron team joins other prominent members in the Linux community by recommending that you upgrade to a 64-bit based architecture.

If you're having trouble using a native Node.js addon with Electron 5.0, there's a chance it needs to be updated to work with the most recent version of V8.

Goodbye v8::Handle, Hello v8::Local​

In 2014, the V8 team deprecated v8::Handle in favor of v8::Local for local handles. Electron 5.0 includes a version of V8 that has finally removed v8::Handle for good, and native Node.js addons that still use it will need to be updated before they can be used with Electron 5.0.

The required code change is minimal, but every native Node module that still uses v8::Handle will fail to build with Electron 5.0 and will need to be modified. The good news is that Node.js v12 will also include this V8 change, so any modules that use v8::Handle will need to be updated anyway to work with the upcoming version of Node.

I maintain a native addon, how can I help?​

If you maintain a native addon for Node.js, ensure you replace all occurrences of v8::Handle with v8::Local. The former was just an alias of the latter, so no other changes need to be made to address this specific issue.

You may also be interested in looking into N-API, which is maintained separately from V8 as a part of Node.js itself, and aims to insulate native addons from changes in the underlying JavaScript engine. You can find more information in the N-API documentation on the Node.js website.

Ayuda! I use a native addon in my app and it won't work!​

If you're consuming a native addon for Node.js in your app and the native addon will not build because of this issue, check with the author of the addon to see if they've released a new version that fixes the problem. If not, reaching out to the author (or opening a Pull Request!) is probably your best bet.

Electron now uses GN to build itself. Here's a discussion of why.

GYP and GN

Cuando Electron fue lanzado por primera vez en 2013, la configuración de compilación de Chromium fue escrita con GYP, abreviando "Generar proyectos".

En 2014, el proyecto Chromium introdujo una nueva herramienta de configuración de construcción llamada GN (abreviatura de "Generar Ninja") los archivos de construcción de Chromium fueron migrados a GN y GYP fue eliminado del código fuente.

Históricamente, Electron ha mantenido una separación entre el código principal de Electron y libchromiumcontent, la parte de Electron que envuelve el 'contenido' de Chromium. Electron has carried on using GYP, while libchromiumcontent -- as a subset of Chromium -- switched to GN when Chromium did.

Like gears that don't quite mesh, there was friction between using the two build systems. Maintaining compatibility was error-prone, from compiler flags and #defines that needed to be meticulously kept in sync between Chromium, Node, V8, and Electron.

To address this, the Electron team has been working on moving everything to GN. Today, the commit to remove the last of the GYP code from Electron was landed in master.

What this means for you

If you're contributing to Electron itself, the process of checking out and building Electron from master or 4.0.0 is very different than it was in 3.0.0 and earlier. See the GN build instructions for details.

If you're developing an app with Electron, there are a few minor changes you might notice in the new Electron 4.0.0-nightly; but more than likely, Electron's change in build system will be totally transparent to you.

What this means for Electron

GN is faster than GYP and its files are more readable and maintainable. Moreover, we hope that using a single build configuration system will reduce the work required to upgrade Electron to new versions of Chromium.

• It's already helped development on Electron 4.0.0 substantially because Chromium 67 removed support for MSVC and switched to building with Clang on Windows. With the GN build, we inherit all the compiler commands from Chromium directly, so we got the Clang build on Windows for free!

• It's also made it easier for Electron to use BoringSSL in a unified build across Electron, Chromium, and Node -- something that was problematic before.

Electron 1.4. 2 contiene un parche importante que soluciona un problema de Chrome en el que algunos Symantec, GeoTrust, y los certificados Thawte SSL/TLS son rechazados incorrectamente 10 semanas desde el tiempo de compilación de libchromiumcontent, La biblioteca Chrome de Electron subyacente. No hay problemas con los certificados utilizados en los sitios afectados y la sustitución de estos certificados no ayudará.

En Electron 1.4.0 — 1.4.11 las solicitudes HTTPS a los sitios que utilicen estos certificados afectados fallarán con errores de red después de una fecha determinada. Esto afecta las solicitudes HTTPS realizadas con las API de red subyacentes de Chrome. como window.fetch,Solicitudes de Ajax, Electron's net API, BrowserWindow.loadURL, webContents.loadURL, el atributo src en una etiqueta <webview> y otros.

Actualizando sus aplicaciones a 1.4.12 evitará que se produzcan estos errores de solicitud.

Nota: Este problema se introdujo en Chrome 53, por lo que las versiones anteriores a Electron 1.4.0 no se ven afectadas.

Fechas de impacto​

A continuación se muestra una tabla de cada versión de Electron 1.4 y la fecha en que las solicitudes a los sitios que utilizan estos certificados afectados comenzarán a fallar.

Puedes verificar la fecha de impacto de tu aplicación adelantando el reloj de tu ordenador y luego comprobar si https://symbeta. ymantec.com/welcome/ carga con éxito.

Más información​

Puede leer más sobre este tema, el problema original y la corrección en los siguientes lugares:

• ¿Qué es la transparencia del certificado?
• Artículo de la base de conocimiento de Symtantec
• Cuestión de Chrome 664177
• Corrección del problema de Chrome 664177
• Parche libchromiumcontent para la incidencia 664177

As of Electron version 1.3.1, you can npm install electron --save-dev to install the latest precompiled version of Electron in your app.

El binario precombinado de Electron​

Si alguna vez has trabajado en una aplicación Electron, probablemente te hayas encontrado con el paquete Npm electron-prebuilt. Este paquete es una parte indispensable de casi todos los proyectos de Electron. Cuando se instala, detecta su sistema operativo y descarga un binario precompilador que está compilado para funcionar en la arquitectura de tu sistema.

Nuevo estado​

The Electron installation process was often a stumbling block for new developers. Many brave people tried to get started developing an Electron by app by running npm install electron instead of npm install electron-prebuilt, only to discover (often after much confusion) that it was not the electron they were looking for.

This was because there was an existing electron project on npm, created before GitHub's Electron project existed. To help make Electron development easier and more intuitive for new developers, we reached out to the owner of the existing electron npm package to ask if he'd be willing to let us use the name. Luckily he was a fan of our project, and agreed to help us repurpose the name.

Prebuilt lives on​

As of version 1.3.1, we have begun publishing electron and electron-prebuilt packages to npm in tandem. The two packages are identical. We chose to continue publishing the package under both names for a while so as not to inconvenience the thousands of developers who are currently using electron-prebuilt in their projects. We recommend updating your package.json files to use the new electron dependency, but we will continue releasing new versions of electron-prebuilt until the end of 2016.

The electron-userland/electron-prebuilt repository will remain the canonical home of the electron npm package.

Many thanks​

We owe a special thanks to @mafintosh, @maxogden, and many other contributors for creating and maintaining electron-prebuilt, and for their tireless service to the JavaScript, Node.js, and Electron communities.

And thanks to @logicalparadox for allowing us to take over the electron package on npm.

. Desbloquear teléfono​

We've worked with the community to update popular packages that are affected by this change. Packages like electron-packager, electron-rebuild, and electron-builder have already been updated to work with the new name while continuing to support the old name.

If you encounter any problems installing this new package, please let us know by opening an issue on the electron-userland/electron-prebuilt repository.

For any other issues with Electron, please use the electron/electron repository.

Atom Shell is now called Electron. Puedes aprender más sobre Electron y lo que la gente está construyendo con él en su nuevo hogar electronjs.org.

Electron es el shell de aplicación multiplataforma que originalmente construimos para el editor Atom para manejar la integración de bucle de eventos Chromium/Node.js y APIs nativas.

Cuando empezamos, nuestro objetivo no era sólo satisfacer las necesidades de un editor de texto. También queríamos crear un marco sencillo que permitiera a la gente utilizar tecnologías web para crear aplicaciones de escritorio multiplataforma con todos los adornos nativos.

En dos años, Electron ha crecido enormemente. Ahora incluye actualizaciones automáticas de aplicaciones, instaladores de Windows, informes de fallos, notificaciones y otras útiles funciones de aplicaciones nativas—, todo ello expuesto a través de API de JavaScript. Y tenemos más en proyecto. Tenemos previsto extraer aún más bibliotecas de Atom para que crear una aplicación nativa con tecnologías web sea lo más fácil posible.

Hasta ahora, desarrolladores individuales, empresas emergentes y grandes compañías han creado aplicaciones con Electron. Han creado una gran variedad de aplicaciones—, como aplicaciones de chat, exploradores de bases de datos, diseñadores de mapas, herramientas de diseño colaborativo y aplicaciones de prototipado móvil.

Echa un vistazo a la nueva electronjs.org para ver más de las aplicaciones que la gente ha construido en Electron o echa un vistazo a los documentos para aprender más acerca de qué más se puede hacer.

Si ya has empezado, nos encantaría charlar contigo sobre las aplicaciones que estás creando en Electron. Envíanos un correo electrónico a info@electronjs.org para contarnos más cosas. También puedes seguir la nueva cuenta de Twitter @ElectronJS para mantenerte conectado con el proyecto.

⚡ 💙 🔌