All the latest news from the Electron team and community. Subscribe to the RSS feed.
The Electron community is growing quickly, and people are creating powerful new apps and tools at an astounding rate. To celebrate this creative momentum and keep the community informed of some of these new projects, we’ve decided to start a weekly blog series featuring noteworthy Electron-related projects.
We recently hosted an Electron hackathon at GitHub HQ for members of Hackbright Academy, a coding school for women founded in San Francisco. To help attendees get a head start on their projects, our own Kevin Sawicki created a few sample Electron applications.
We’ve added a new userland section to the Electron website to help users discover the people, packages, and apps that make up our flourishing open-source ecosystem.
Electron 1.4.12 contains an important patch that fixes an upstream Chrome issue where some Symantec, GeoTrust, and Thawte SSL/TLS certificates are incorrectly rejected 10 weeks from the build time of libchromiumcontent, Electron’s underlying Chrome library. There are no issues with the certificates used on the affected sites and replacing these certificates will not help.
Here are the new Electron apps and talks that were added to the site in September.
Today we’re announcing some improvements to Electron’s documentation. Every new release now includes a JSON file that describes all of Electron’s public APIs in detail. We created this file to enable developers to use Electron’s API documentation in interesting new ways.
This post introduces the concept of weak references and how they are used to manage resources in Electron.
Here are the new Electron apps that were added to the site in August.
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.
This is the second post in an ongoing series explaining the internals of Electron. Check out the first post about event loop integration if you haven’t already.
Most people use Node for server-side applications, but because of Node’s rich API set and thriving community, it is also a great fit for an embedded library. This post explains how Node is used as a library in Electron.
We’re starting a monthly roundup to highlight activity in the Electron community. Each roundup will feature things like new apps, upcoming meetups, tools, videos, etc.
This is the first post of a series that explains the internals of Electron. This post introduces how Node’s event loop is integrated with Chromium in Electron.
Looking for an introduction to Electron? Two new podcasts have just been released that give a great overview of what it is, why it was built, and how it is being used.
0.37 was recently released and included a major upgrade from Chrome 47 to Chrome 49 and also several new core APIs. This latest release brings in all the new features shipped in Chrome 48 and Chrome 49. This includes CSS custom properties, increased ES6 support,
Promise improvements, and many other new features now available in your Electron app.
Building an Electron application means you only need to create one codebase and design for one browser, which is pretty handy. But because Electron stays up to date with Node.js and Chromium as they release, you also get to make use of the great features they ship with. In some cases this eliminates dependencies you might have previously needed to include in a web app.
Recently Electron added two exciting features: a Mac App Store compatible build and a built-in Windows auto updater.
There have been some interesting updates and talks given on Electron recently, here’s a roundup.
Join us September 29th at GitHub’s HQ for an Electron meetup hosted by Atom team members @jlord and @kevinsawicki. There will be talks, food to snack on, and time to hangout and meet others doing cool things with Electron. We’ll also have a bit of time to do lightning talks for those interested. Hope to see you there!
This week we’ve given Electron’s documentation a home on electron.atom.io. You can visit /docs/latest for the latest set of docs. We’ll keep versions of older docs, too, so you’re able to visit /docs/vX.XX.X for the docs that correlate to the version you’re using.
Atom Shell is now called Electron. You can learn more about Electron and what people are building with it at its new home electron.atom.io.