发现了一个漏洞，该漏洞允许在某些禁用 Node.js 集成的 Electron 应用中重新启用 Node.js 集成。该漏洞已被分配 CVE 标识符 CVE-2018-1000136。

🌐 A vulnerability has been discovered which allows Node.js integration to be re-enabled in some Electron applications that disable it. This vulnerability has been assigned the CVE identifier CVE-2018-1000136.

受影响的应用​

🌐 Affected Applications

如果以下所有情况都成立，则应用会受到影响：

🌐 An application is affected if all of the following are true:

1. 可在 Electron 1.7、1.8 或 2.0.0-beta 版本上运行
2. 允许执行任意远程代码
3. 禁用 Node.js 集成
4. 在其 webPreferences 中未明确声明 webviewTag: false
5. 未启用 nativeWindowOption 选项
6. 不会拦截 new-window 事件，并且在不使用提供的 options 标签的情况下手动覆盖 event.newGuest

虽然这似乎只存在于少数 Electron 应用中，但我们建议所有应用升级以防万一。

🌐 Although this appears to be a minority of Electron applicatons, we encourage all applications to be upgraded as a precaution.

缓解措施​

🌐 Mitigation

此漏洞已在今天发布的 1.7.13、1.8.4 和 2.0.0-beta.5 版本中修复。

🌐 This vulnerability is fixed in today's 1.7.13, 1.8.4, and 2.0.0-beta.5 releases.

无法升级应用 Electron 版本的开发者可以使用以下代码缓解此漏洞：

🌐 Developers who are unable to upgrade their application's Electron version can mitigate the vulnerability with the following code:

app.on('web-contents-created', (event, win) => {
  win.on(
    'new-window',
    (event, newURL, frameName, disposition, options, additionalFeatures) => {
      if (!options.webPreferences) options.webPreferences = {};
      options.webPreferences.nodeIntegration = false;
      options.webPreferences.nodeIntegrationInWorker = false;
      options.webPreferences.webviewTag = false;
      delete options.webPreferences.preload;
    },
  );
});

// and *IF* you don't use WebViews at all,
// you might also want
app.on('web-contents-created', (event, win) => {
  win.on('will-attach-webview', (event, webPreferences, params) => {
    event.preventDefault();
  });
});

更多信息​

🌐 Further Information

这个漏洞是由 Trustwave SpiderLabs 的 Brendan Scarvell 发现并负责任地报告给 Electron 项目的。

🌐 This vulnerability was found and reported responsibly to the Electron project by Brendan Scarvell of Trustwave SpiderLabs.

要了解有关保持 Electron 应用安全的最佳实践的更多信息，请参阅我们的 安全教程。

🌐 To learn more about best practices for keeping your Electron apps secure, see our security tutorial.

如果你希望报告 Electron 中的漏洞，请提交 [GitHub 安全咨询]。

🌐 Please file a GitHub Security Advisory if you wish to report a vulnerability in Electron.

请加入我们的email list以接收有关版本发布和安全更新的通知。

🌐 Please join our email list to receive updates about releases and security updates.

上周，electronjs.org 网站有几分钟的停机。如果你受到这些短暂中断的影响，我们对此带来的不便表示歉意。经过今天的一些调查，我们已经诊断出根本原因，并部署了一个修复。

🌐 Last week the electronjs.org site had a few minutes of downtime. If you were affected by these brief outages, we're sorry for the inconvenience. After a bit of investigation today, we've diagnosed the root cause and have deployed a fix.

为了防止将来出现这种停机情况，我们已经在我们的应用上启用了Heroku 阈值警报。每当我们的 Web 服务器累积的失败请求或响应缓慢超过某个阈值时，我们的团队将会收到通知，以便我们能够快速解决问题。

🌐 To prevent this kind of downtime in the future, we've enabled Heroku threshold alerts on our app. Any time our web server accumulates failed requests or slow responses beyond a certain threshold, our team will be notified so we can address the problem quickly.

所有语言的离线文档​

🌐 Offline Docs in Every Language

下次当你在飞机上或地下咖啡馆开发 Electron 应用时，可能会希望拥有一份离线文档以供参考。幸运的是，Electron 的文档以 Markdown 文件形式提供，并且有超过 20 种语言版本。

🌐 The next time you're developing an Electron app on a plane or in a subterranean coffee shop, you might want to have a copy of the docs for offline reference. Fortunately, Electron's docs are available as Markdown files in over 20 languages.

git clone https://github.com/electron/electron-i18n
ls electron-i18n/content

带有图形用户界面的离线文档​

🌐 Offline Docs with a GUI

devdocs.io/electron 是一个方便的网站，提供离线文档，不仅仅适用于 Electron，还包括许多其他项目，如 JavaScript、TypeScript、Node.js、React、Angular 等等。当然，也有针对它的 Electron 应用。
可以查看 devdocs-app 在 Electron 网站上的信息。

如果你想在不使用鼠标或触控板的情况下安装应用，可以尝试使用 Electron Forge 的 install 命令：

🌐 If you like to install apps without using your mouse or trackpad, give Electron Forge's install command a try:

npx electron-forge install egoist/devdocs-app

已经发现了一个影响使用自定义协议处理程序的 Electron 应用的远程代码执行漏洞。该漏洞已被分配 CVE 标识符 CVE-2018-1000006。

🌐 A remote code execution vulnerability has been discovered affecting Electron apps that use custom protocol handlers. This vulnerability has been assigned the CVE identifier CVE-2018-1000006.

受影响的平台​

🌐 Affected Platforms

在 Windows 上运行的 Electron 应用，如果将自己注册为某个协议（如 myapp://）的默认处理程序，就存在漏洞。

🌐 Electron apps designed to run on Windows that register themselves as the default handler for a protocol, like myapp://, are vulnerable.

无论协议如何注册，例如使用本地代码、Windows 注册表或 Electron 的 app.setAsDefaultProtocolClient API，这类应用都可能受到影响。

🌐 Such apps can be affected regardless of how the protocol is registered, e.g. using native code, the Windows registry, or Electron's app.setAsDefaultProtocolClient API.

macOS 和 Linux 不受此问题影响。

🌐 macOS and Linux are not vulnerable to this issue.

缓解措施​

🌐 Mitigation

我们已经发布了包含此漏洞修复的新版本 Electron： 1.8.2-beta.5、 1.7.12、 和 1.6.17。 我们强烈建议所有 Electron 开发者立即将他们的应用更新到最新的稳定版本。

🌐 We've published new versions of Electron which include fixes for this vulnerability: 1.8.2-beta.5, 1.7.12, and 1.6.17. We urge all Electron developers to update their apps to the latest stable version immediately.

如果由于某种原因你无法升级 Electron 版本， 你可以在调用 app.setAsDefaultProtocolClient 时将 -- 作为最后一个参数附加，这可以防止 Chromium 解析更多选项。 双破折号 -- 表示命令选项的结束，之后只接受位置参数。

🌐 If for some reason you are unable to upgrade your Electron version, you can append -- as the last argument when calling app.setAsDefaultProtocolClient, which prevents Chromium from parsing further options. The double dash -- signifies the end of command options, after which only positional parameters are accepted.

app.setAsDefaultProtocolClient(protocol, process.execPath, [
  '--your-switches-here',
  '--',
]);

有关更多详情，请参阅 app.setAsDefaultProtocolClient API。

🌐 See the app.setAsDefaultProtocolClient API for more details.

要了解有关保持你的 Electron 应用安全的最佳做法，请参阅我们的 [安全教程]。

🌐 To learn more about best practices for keeping your Electron apps secure, see our security tutorial.

如果你希望报告 Electron 中的漏洞，请提交 [GitHub 安全咨询]。

🌐 Please file a GitHub Security Advisory if you wish to report a vulnerability in Electron.

Electron 正在开发一个新的主要版本，同时我们对版本控制策略也进行了一些调整。从 2.0.0 版本开始，Electron 将严格遵循语义化版本控制（Semantic Versioning）。

🌐 A new major version of Electron is in the works, and with it some changes to our versioning strategy. As of version 2.0.0, Electron will strictly adhere to Semantic Versioning.

这一变化意味着你会更频繁地看到主版本的提升，而且通常会是对 Chromium 的重大更新。补丁版本也将更加稳定，因为它们现在只包含错误修复，不会有新功能。

🌐 This change means you'll see the major version bump more often, and it will usually be a major update to Chromium. Patch releases will also be more stable, as they will now only contain bug fixes with no new features.

主要版本更新

• Chrom 版本更新
• Node.js 主要版本更新
• Electron 断裂 API 更改

次要版本更新

• Node.js 小版本更新
• Electron 不间断 API 更改

补丁版本递增

• Node.js 补丁版本更新
• 修复相关的 chromium 补丁
• Electron 错误修复

因为 Electron 的 semver 范围现在将更有意义，我们建议使用 npm 的默认 --save-dev 标志来安装 Electron，这将为你的版本加上 ^ 前缀，使你能够安全地保持次要和修补程序更新：

🌐 Because Electron's semver ranges will now be more meaningful, we recommend installing Electron using npm's default --save-dev flag, which will prefix your version with ^, keeping you safely up to date with minor and patch updates:

npm install --save-dev electron

对于只对错误修复感兴趣的开发者，你应该使用波浪号语义版本前缀，例如 ~2.0.0，它不会引入新功能，只会进行修复以提高稳定性。

🌐 For developers interested only in bug fixes, you should use the tilde semver prefix e.g. ~2.0.0, which which will never introduce new features, only fixes to improve stability.

欲了解更多详情，请参见 electronjs.org/docs/tutorial/electron-versioning。

🌐 For more details, see electronjs.org/docs/tutorial/electron-versioning.

Electron 有了一个新网站，网址是 electronjs.org！我们已将原来的静态 Jekyll 网站替换为 Node.js 网络服务器，这让我们能够更灵活地进行网站的国际化，并为更多令人兴奋的新功能铺平了道路。

🌐 Electron has a new website at electronjs.org! We've replaced our static Jekyll site with a Node.js webserver, giving us flexibility to internationalize the site and paving the way for more exciting new features.

🌍 翻译​

🌐 🌍 Translations

我们已开始着手对网站进行国际化，目标是让全球开发者都能轻松进行 Electron 应用开发。我们正在使用一个名为 Crowdin 的本地化平台，该平台可以与 GitHub 集成，并在内容被翻译成不同语言时自动创建和更新拉取请求。

🌐 We've begun the process of internationalizing the website with the goal of making Electron app development accessible to a global audience of developers. We're using a localization platform called Crowdin that integrates with GitHub, opening and updating pull requests automatically as content is translated into different languages.

尽管到目前为止我们一直在默默地推进这项工作，但已经有超过75名Electron社区成员自发发现了这个项目，并加入了将网站国际化及将Electron文档翻译成20多种语言的工作。我们看到来自世界各地的每日贡献，其中法语、越南语、印尼语和中文的翻译工作走在前列。

🌐 Though we've been working quietly on this effort so far, over 75 Electron community members have already discovered the project organically and joined in the effort to internationalize the website and translate Electron's docs into over 20 languages. We are seeing daily contributions from people all over the world, with translations for languages like French, Vietnamese, Indonesian, and Chinese leading the way.

要选择你的语言并查看翻译进度，请访问 electronjs.org/languages

🌐 To choose your language and view translation progress, visit electronjs.org/languages

如果你会多种语言并且有兴趣帮助翻译 Electron 的文档和网站，可以访问 electron/electron-i18n 仓库，或者直接在 Crowdin 上进行翻译，你可以使用 GitHub 账号登录。

🌐 If you're multilingual and interested in helping translate Electron's docs and website, visit the electron/electron-i18n repo, or jump right into translating on Crowdin, where you can sign in using your GitHub account.

目前，Electron 项目在 Crowdin 上已启用 21 种语言。添加对更多语言的支持很简单，因此如果你有兴趣帮助翻译，但没有看到你的语言列在其中，请告诉我们，我们会启用它。

🌐 There are currently 21 languages enabled for the Electron project on Crowdin. Adding support for more languages is easy, so if you're interested in helping translate but you don't see your language listed, let us know and we'll enable it.

原始翻译文档​

🌐 Raw Translated Docs

如果你更喜欢阅读原始 Markdown 文件的文档，现在你可以用任何语言这样做：

🌐 If you prefer to read documentation in raw markdown files, you can now do that in any language:

git clone https://github.com/electron/electron-i18n
ls electron-i18n/content

应用页面​

🌐 App Pages

截至今天，任何 Electron 应用都可以轻松在 Electron 网站上拥有自己的页面。举几个例子，看看 Etcher、1Clipboard 或 GraphQL Playground，如图所示，在网站的日文版上：

🌐 As of today, any Electron app can easily have its own page on the Electron site. For a few examples, check out Etcher, 1Clipboard, or GraphQL Playground, pictured here on the Japanese version of the site:

有一些非常棒的 Electron 应用，但它们并不总是容易找到，而且并不是每个开发者都有时间或资源去建立一个完善的网站来推广和分发他们的应用。

🌐 There are some incredible Electron apps out there, but they're not always easy to find, and not every developer has the time or resources to build a proper website to market and distribute their app.

仅使用一个PNG 图标文件和少量应用元数据，我们就能够收集有关特定应用的大量信息。通过收集 GitHub 的数据，应用页面现在可以显示截图、下载链接、版本、更新说明以及每个拥有公共仓库的应用的 README。通过从每个应用的图标中提取调色板，我们可以制作大胆且易于识别的颜色，为每个应用页面提供一定的视觉差异。

🌐 Using just a PNG icon file and a small amount of app metadata, we're able to collect a lot of information about a given app. Using data collected from GitHub, app pages can now display screenshots, download links, versions, release notes, and READMEs for every app that has a public repository. Using a color palette extracted from each app's icon, we can produce bold and accessible colors to give each app page some visual distinction.

应用索引页面 现在也有分类和关键字过滤功能，方便查找有趣的应用，如 GraphQL 图形界面 和 点对点工具。

🌐 The apps index page now also has categories and a keyword filter to find interesting apps like GraphQL GUIs and p2p tools.

如果你有一个想在网站上展示的 Electron 应用，可以在 electron/electron-apps 仓库中提交一个 pull request。

🌐 If you've got an Electron app that you'd like featured on the site, open a pull request on the electron/electron-apps repository.

使用 Homebrew 的一行安装​

🌐 One-line Installation with Homebrew

macOS 的 Homebrew 包管理器有一个名为 cask 的子命令，它可以让你通过在终端中输入一个命令轻松安装桌面应用，例如 brew cask install atom。

🌐 The Homebrew package manager for macOS has a subcommand called cask that makes it easy to install desktop apps using a single command in your terminal, like brew cask install atom.

我们已经开始收集流行 Electron 应用的 Homebrew cask 名称，并且现在在每个有 cask 的应用页面上显示安装命令（针对 macOS 访问者）:

🌐 We've begun collecting Homebrew cask names for popular Electron apps and are now displaying the installation command (for macOS visitors) on every app page that has a cask:

要查看所有具有 Homebrew Cask 名称的应用，请访问 electronjs.org/apps?q=homebrew。如果你知道其他我们尚未收录的 Cask 应用，请添加它们！

🌐 To view all the apps that have homebrew cask names, visit electronjs.org/apps?q=homebrew. If you know of other apps with casks that we haven't indexed yet, please add them!

🌐 一个新字段​

🌐 🌐 A New Domain

我们已将网站从 electron.atom.io 迁移到新的域名：electronjs.org。

🌐 We've moved the site from electron.atom.io to a new domain: electronjs.org.

Electron 项目诞生于 Atom 内部，Atom 是 GitHub 基于 web 技术构建的开源文本编辑器。Electron 最初被称为 atom-shell。Atom 是第一个使用它的应用，但人们很快就意识到，这个神奇的 Chromium + Node 运行时可以用于各种不同的应用。当像微软和 Slack 这样的公司开始使用 atom-shell 时，很明显这个项目需要一个新的名字。

🌐 The Electron project was born inside Atom, GitHub's open-source text editor built on web technologies. Electron was originally called atom-shell. Atom was the first app to use it, but it didn't take long for folks to realize that this magical Chromium + Node runtime could be used for all kinds of different applications. When companies like Microsoft and Slack started to make use of atom-shell, it became clear that the project needed a new name.

于是，“Electron”诞生了。在2016年初，GitHub组建了一个新的团队，专门专注于Electron的开发和维护，独立于Atom。在此之后，Electron被成千上万的应用开发者采用，如今许多大型公司也依赖它，其中许多公司还有自己的Electron团队。

🌐 And so "Electron" was born. In early 2016, GitHub assembled a new team to focus specifically on Electron development and maintenance, apart from Atom. In the time since, Electron has been adopted by thousands of app developers, and is now depended on by many large companies, many of which have Electron teams of their own.

支持 GitHub 的 Electron 项目，比如 Atom 和 GitHub Desktop，仍然是我们团队的优先事项，但通过迁移到一个新的域名，我们希望能够帮助澄清 Atom 和 Electron 之间的技术区别。

🌐 Supporting GitHub's Electron projects like Atom and GitHub Desktop is still a priority for our team, but by moving to a new domain we hope to help clarify the technical distinction between Atom and Electron.

🐢🚀 Node.js 无处不在​

🌐 🐢🚀 Node.js Everywhere

之前的 Electron 网站是使用流行的基于 Ruby 的静态网站生成器 Jekyll 构建的。Jekyll 是构建静态网站的绝佳工具，但网站已经开始超出它的能力范围。我们希望拥有更多动态功能，例如正确的重定向和动态内容渲染，因此 Node.js 服务器成为显而易见的选择。

🌐 The previous Electron website was built with Jekyll, the popular Ruby-based static site generator. Jekyll is a great tool for building static websites, but the website had started to outgrow it. We wanted more dynamic capabilities like proper redirects and dynamic content rendering, so a Node.js server was the obvious choice.

Electron生态系统包含使用多种不同编程语言编写组件的项目，从Python到C++再到Bash。但JavaScript是Electron的基础语言，也是我们社区中使用最广泛的语言。

🌐 The Electron ecosystem includes projects with components written in many different programming languages, from Python to C++ to Bash. But JavaScript is foundational to Electron, and it's the language used most in our community.

通过将网站从 Ruby 迁移到 Node.js，我们旨在降低希望为网站做出贡献的人的入门门槛。

🌐 By migrating the website from Ruby to Node.js, we aim to lower the barrier to entry for people wishing to contribute to the website.

⚡️ 更轻松的开源参与​

🌐 ⚡️ Easier Open-Source Participation

如果你的系统上已经安装了 Node.js（8 或更高版本）和 git，你可以轻松地在本地运行该网站：

🌐 If you've got Node.js (8 or higher) and git installed on your system, you can easily get the site running locally:

git clone https://github.com/electron/electronjs.org
cd electronjs.org
npm install
npm run dev

新网站托管在 Heroku 上。我们使用部署流水线和Review Apps功能，该功能会为每个拉取请求自动创建一个正在运行的应用副本。这使得审查者可以轻松查看拉取请求对网站实时副本的实际影响。

🌐 The new website is hosted on Heroku. We use deployment pipelines and the Review Apps feature, which automatically creates a running copy of the app for every pull request. This makes it easy for reviewers to view the actual effects of a pull request on a live copy of the site.

🙏 感谢所有贡献者​

🌐 🙏 Thanks to Contributors

我们想向世界各地所有贡献了时间和精力帮助改进 Electron 的朋友们表示特别感谢。开源社区的热情在 Electron 的成功中起到了不可估量的作用。谢谢大家！

🌐 We'd like to give special thanks to all the folks around the world who have contributed their own time and energy to help improve Electron. The passion of the open-source community has helped immeasurably in making Electron a success. Thank you!

在 Google Chromium 中发现了一个远程代码执行漏洞，影响所有最近版本的 Electron。任何访问远程内容的 Electron 应用都容易受到此漏洞的攻击，无论是否启用了 [沙箱选项]。

🌐 A remote code execution vulnerability has been discovered in Google Chromium that affects all recent versions of Electron. Any Electron app that accesses remote content is vulnerable to this exploit, regardless of whether the sandbox option is enabled.

我们发布了两个新的 Electron 版本 1.7.8 和 1.6.14，其中都包含了对该漏洞的修复。我们强烈建议所有 Electron 开发者立即将他们的应用更新到最新的稳定版本：

🌐 We've published two new versions of electron 1.7.8 and 1.6.14, both of which include a fix for this vulnerability. We urge all Electron developers to update their apps to the latest stable version immediately:

npm i electron@latest --save-dev

要了解有关保持你的 Electron 应用安全的最佳做法，请参阅我们的 [安全教程]。

🌐 To learn more about best practices for keeping your Electron apps secure, see our security tutorial.

如果你希望报告 Electron 中的漏洞，请提交 [GitHub 安全咨询]。

🌐 Please file a GitHub Security Advisory if you wish to report a vulnerability in Electron.

electron npm 包现在包含一个 TypeScript 定义文件，提供了对整个 Electron API 的详细注释。这些注释可以提升你的 Electron 开发体验，即使你使用的是普通的 JavaScript。只需 npm install electron 就可以在你的项目中获取最新的 Electron 类型定义。

🌐 The electron npm package now includes a TypeScript definition file that provides detailed annotations of the entire Electron API. These annotations can improve your Electron development experience even if you're writing vanilla JavaScript. Just npm install electron to get up-to-date Electron typings in your project.

TypeScript 是由微软创建的一种开源编程语言。它是 JavaScript 的超集，通过添加对静态类型的支持来扩展语言。近年来，TypeScript 社区发展迅速，在最近的 Stack Overflow 开发者调查中，TypeScript 被评为最受喜爱的编程语言之一。TypeScript 被形容为“可扩展的 JavaScript”，GitHub、Slack 和 Microsoft 的团队都在使用它来编写可扩展的 Electron 应用，这些应用被数百万人使用。

🌐 TypeScript is an open-source programming language created by Microsoft. It's a superset of JavaScript that extends the language by adding support for static types. The TypeScript community has grown quickly in recent years, and TypeScript was ranked among the most loved programming languages in a recent Stack Overflow developer survey. TypeScript is described as "JavaScript that scales", and teams at GitHub, Slack, and Microsoft are all using it to write scalable Electron apps that are used by millions of people.

TypeScript 支持 JavaScript 中的许多新语言特性，比如类、对象解构和 async/await，但它真正的区别特性是类型注解。 声明程序预期的输入和输出数据类型可以减少错误，通过帮助你在编译时发现错误，同时这些注解也可以作为对程序工作方式的正式声明。

🌐 TypeScript supports many of the newer language features in JavaScript like classes, object destructuring, and async/await, but its real differentiating feature is type annotations. Declaring the input and output datatypes expected by your program can reduce bugs by helping you find errors at compile time, and the annotations can also serve as a formal declaration of how your program works.

当库使用原生 JavaScript 编写时，类型通常在编写文档时作为附带考虑而被模糊定义。函数通常可以接受的类型比文档中记录的更多，或者函数可能具有未记录的隐形约束，这可能导致运行时错误。

🌐 When libraries are written in vanilla Javascript, the types are often vaguely defined as an afterthought when writing documentation. Functions can often accept more types than what was documented, or a function can have invisible constraints that are not documented, which can lead to runtime errors.

TypeScript 通过 定义文件 解决了这个问题。TypeScript 定义文件描述了一个库的所有函数以及其预期的输入和输出类型。当库的作者在发布的库中打包 TypeScript 定义文件时，该库的使用者可以直接在编辑器中探索它的 API 并立即开始使用，通常无需查阅库的文档。

🌐 TypeScript solves this problem with definition files. A TypeScript definition file describes all the functions of a library and its expected input and output types. When library authors bundle a TypeScript definition file with their published library, consumers of that library can explore its API right inside their editor and start using it right away, often without needing to consult the library's documentation.

许多流行的项目，例如 Angular、Vue.js、node-github（以及现在的 Electron！）都会编译自己的定义文件，并将其与发布的 npm 包一起打包。对于那些没有打包自己定义文件的项目，有 DefinitelyTyped，这是一个由社区维护的第三方定义文件生态系统。

🌐 Many popular projects like Angular, Vue.js, node-github (and now Electron!) compile their own definition file and bundle it with their published npm package. For projects that don't bundle their own definition file, there is DefinitelyTyped, a third-party ecosystem of community-maintained definition files.

安装​

🌐 Installation

从版本 1.6.10 开始，每个 Electron 版本都包含自己的 TypeScript 定义文件。当你从 npm 安装 electron 包时，electron.d.ts 文件会随安装的包自动打包。

🌐 Starting at version 1.6.10, every release of Electron includes its own TypeScript definition file. When you install the electron package from npm, the electron.d.ts file is bundled automatically with the installed package.

安装 Electron 最安全的方法是使用确切的版本号：

🌐 The safest way to install Electron is using an exact version number:

npm install electron --save-dev --save-exact

或者如果你使用的是 yarn:

🌐 Or if you're using yarn:

yarn add electron --dev --exact

如果你已经在使用第三方定义，例如 @types/electron 和 @types/node，你应该将它们从你的 Electron 项目中移除，以防止任何冲突。

🌐 If you were already using third-party definitions like @types/electron and @types/node, you should remove them from your Electron project to prevent any collisions.

定义文件来源于我们的结构化 API 文档，因此它始终与Electron 的 API 文档保持一致。只需安装 electron，你就可以始终获得与所使用的 Electron 版本同步的 TypeScript 定义。

🌐 The definition file is derived from our structured API documentation, so it will always be consistent with Electron's API documentation. Just install electron and you'll always get TypeScript definitions that are up to date with the version of Electron you're using.

用法​

🌐 Usage

想要了解如何安装和使用 Electron 的新 TypeScript 注解，请观看这个简短的演示录屏：

🌐 For a summary of how to install and use Electron's new TypeScript annotations, watch this short demo screencast:

如果你正在使用 Visual Studio Code，你已经拥有内置的 TypeScript 支持。还有社区维护的插件可用于 Atom、Sublime、vim 以及 其他编辑器。

🌐 If you're using Visual Studio Code, you've already got TypeScript support built in. There are also community-maintained plugins for Atom, Sublime, vim, and other editors.

一旦你的编辑器配置好了 TypeScript，你就会开始看到更多上下文感知的功能，比如自动补全建议、内联方法引用、参数检查等。

🌐 Once your editor is configured for TypeScript, you'll start to see more context-aware behavior like autocomplete suggestions, inline method reference, argument checking, and more.

TypeScript 入门​

🌐 Getting started with TypeScript

如果你是 TypeScript 新手并想了解更多，这个来自微软的入门视频提供了对该语言创建原因、工作原理、使用方法以及未来发展方向的不错概述。

🌐 If you're new to TypeScript and want to learn more, this introductory video from Microsoft provides a nice overview of why the language was created, how it works, how to use it, and where it's headed.

官方 TypeScript 网站上还有一本手册和一个练习场。

🌐 There's also a handbook and a playground on the official TypeScript website.

由于 TypeScript 是 JavaScript 的超集，你现有的 JavaScript 代码已经是有效的 TypeScript。这意味着你可以逐步将现有的 JavaScript 项目迁移到 TypeScript，根据需要逐步加入新的语言特性。

🌐 Because TypeScript is a superset of JavaScript, your existing JavaScript code is already valid TypeScript. This means you can gradually transition an existing JavaScript project to TypeScript, sprinkling in new language features as needed.

致谢​

🌐 Thanks

这个项目如果没有 Electron 开源维护者社区的帮助是不可能实现的。感谢 Samuel Attard、Felix Rieseberg、Birunthan Mohanathas、Milan Burda、Brendan Forster 以及其他许多人在修复漏洞、改进文档和技术指导方面的贡献。

🌐 This project would not have been possible without the help of Electron's community of open-source maintainers. Thanks to Samuel Attard, Felix Rieseberg, Birunthan Mohanathas, Milan Burda, Brendan Forster, and many others for their bug fixes, documentation improvements, and technical guidance.

支持​

🌐 Support

如果你在使用 Electron 的新 TypeScript 定义文件时遇到任何问题，请在 electron-typescript-definitions 仓库中提交问题。

🌐 If you encounter any issues using Electron's new TypeScript definition files, please file an issue on the electron-typescript-definitions repository.

祝你 TypeScript 愉快！

🌐 Happy TypeScripting!

本周我们采访了Jasper的创作者，这是一款基于Electron的GitHub通知管理工具。

🌐 This week we interviewed the creator of Jasper, an Electron-based tool for managing GitHub notifications.

你好！你是谁？​

🌐 Hello! Who are you?

我是Ryo Maruyama，在日本的一个软件开发者。我正在开发Jasper和ESDoc。

🌐 I'm Ryo Maruyama, a software developer in Japan. I am developing Jasper and ESDoc.

什么是 Jasper？​

🌐 What is Jasper?

Jasper 是一个灵活且功能强大的 GitHub 问题阅读器。它支持 github.com 和 GitHub Enterprise 上的问题和拉取请求。

为什么要这样做？​

🌐 Why did you make it?

当人们在工作或开源项目活动中使用 GitHub 时，他们往往每天会收到大量通知。作为订阅通知的一种方式，GitHub 提供了电子邮件和网页通知。我使用这些功能有几年时间，但遇到了以下问题：

🌐 When people use GitHub in their job or OSS activities, they tend to receive many notifications on a daily basis. As a way to subscribe to the notifications, GitHub provides email and web notifications. I used these for a couple of years, but I faced the following problems:

• 我很容易忽略别人提到我、我评论过或我正在关注的问题。
• 我把一些问题记在脑子里，以便以后检查，但有时我会忘记它们。
• 为了避免忘记问题，我会在浏览器中保持多个标签页打开。
• 很难检查所有与我相关的问题。
• 很难掌握团队的所有活动。

我花费了大量时间和精力来避免这些问题，因此我决定为 GitHub 创建一个问题阅读器来有效地解决这些问题，并开始开发 Jasper。

🌐 I was spending a lot of time and energy trying to prevent those problems, so I decided to make an issue reader for GitHub to solve these problems efficiently, and started developing Jasper.

谁在使用 Jasper？​

🌐 Who's using Jasper?

Jasper 被多家公司中使用 GitHub 的开发者、设计师和经理使用。当然，一些开源软件开发者也在使用它。它也被 GitHub 的一些人使用！

🌐 Jasper is used by developers, designers, and managers in several companies that are using GitHub. Of course, some OSS developers also are using it. And it is also used by some people at GitHub!

Jasper 如何工作？​

🌐 How does Jasper work?

一旦 Jasper 配置完成，屏幕会显示如下。从左到右，你可以看到“流列表”、“问题列表”和“问题内容”。

🌐 Once Jasper is configured, the following screen appears. From left to right, you can see "streams list", "issues list" and "issue body".

这个“流”是 Jasper 的核心功能。例如，如果你想查看“分配给 electron/electron 仓库中 @zeke 的问题”，你可以创建如下流：

🌐 This "stream" is the core feature of Jasper. For example, if you want to see "issues that are assigned to @zeke in the electron/electron repository", you create the following stream:

repo:electron/electron assignee:zeke is:issue

创建流并等待几秒钟后，你可以看到符合条件的问题。

🌐 After creating the stream and waiting for a few seconds, you can see the issues that meet the conditions.

我们能用流做什么？​

🌐 What can we do with streams?

我将介绍哪些类型的条件可用于流。

🌐 I will introduce what kind of conditions can be used for stream.

用户和团队​

🌐 Users and Teams

involves 意思是 mention、author、assignee 或 commenter

代码库和组织​

🌐 Repositories and Organizations

org 与 user 相同

属性​

🌐 Attributes

审核状态​

🌐 Review Status

正如你可能已经注意到的，通过查看这些内容，流可以使用 GitHub 的搜索查询。有关如何使用流和搜索查询的详细信息，请参阅以下网址。

🌐 As you may have noticed by looking at these, streams can use GitHub's search queries. For details on how to use streams and search queries, see the following URLs.

• jasperapp.io/doc.html#stream
• help.github.com/articles/searching-issues
• help.github.com/articles/search-syntax

Jasper 还具有未读问题管理、未读评论管理、标记星标、通知更新、问题过滤、键盘快捷键等功能。

🌐 Jasper also has features for unread issue management, unread comment management, marking stars, notification updating, filtering issues, keyboard shortcuts, etc.

Jasper 是付费产品吗？它多少钱？​

🌐 Is Jasper a paid product? How much does it cost?

Jasper 价格为 12 美元。不过你可以使用 免费试用版 试用 30 天。

🌐 Jasper is $12. However you can use the free trial edition for 30 days.

为什么选择在 Electron 上构建 Jasper？​

🌐 Why did you choose to build Jasper on Electron?

我喜欢 Electron 的以下几个方面：

🌐 I like the following aspects of Electron:

• 应用可以使用 JavaScript/CSS/HTML 开发。
• 应用可以构建于 Windows、Mac 和 Linux 平台。
• Electron 正在积极开发中，并拥有庞大的社区。

这些功能使桌面应用的开发快速且简单。太棒了！如果你有任何产品创意，你绝对应该考虑使用 Electron。

🌐 These features enable rapid and simple desktop application development. It is awesome! If you have any product idea, you should consider using Electron by all means.

在开发 Jasper 的进程中，你遇到了哪些挑战？​

🌐 What are some challenges you've faced while developing Jasper?

我在理解“流”（stream）概念时遇到了很大困难。起初，我考虑使用 GitHub 的 [通知 API]。然而，我注意到它不支持某些使用场景。之后，我又考虑了结合通知 API 的 [问题 API] 和 [拉取请求 API]。但这始终不是我想要的。然后在思考各种方法时，我意识到轮询 GitHub 的 [搜索 API] 会提供最大的灵活性。经过大约一个月的实验才达到这一点，随后我在两天内实现了带有流概念的 Jasper 原型。

🌐 I had a hard time figuring out the "stream" concept. At first I considered using GitHub's Notifications API. However I noticed that it does not support certain use cases. After that I considered using the Issues API and Pull Requests API, in addition to the Notification API. But it never became what I wanted. Then while thinking about various methods, I realized that polling GitHub's Search API would offer the most flexibility. It took about a month of experimentation to get to this point, then I implemented a prototype of Jasper with the stream concept in two days.

注意：轮询最多每 10 秒进行一次。这对于 GitHub API 的限制来说已经足够了。

🌐 Note: The polling is limited to once every 10 seconds at most. This is acceptable enough for the restriction of GitHub API.

下一步计划是什么？​

🌐 What's coming next?

我计划开发以下功能：

🌐 I have a plan to develop the following features:

• 过滤流：一个流有一些过滤流，用于过滤流中的问题。它就像SQL中的视图。
• 多个账户：你将能够同时使用 github.com 和 GHE
• 提升性能：目前 WebView 的加载速度比普通浏览器慢。

在 Twitter 上关注 @jasperappio 获取更新。

🌐 Follow @jasperappio on Twitter for updates.

本周，我们与@feross和@dcposch聊了聊WebTorrent，这是一款由网络驱动的种子客户端，可以将用户连接在一起，形成一个分布式、去中心化的浏览器对浏览器网络。

🌐 This week we caught up with @feross and @dcposch to talk about WebTorrent, the web-powered torrent client that connects users together to form a distributed, decentralized browser-to-browser network.

什么是 WebTorrent？​

🌐 What is WebTorrent?

WebTorrent 是第一个可以在浏览器中运行的种子客户端。它完全用 JavaScript 编写，并且可以使用 WebRTC 进行点对点传输。不需要浏览器插件、扩展或安装。

WebTorrent 使用开放的 Web 标准，将网站用户连接在一起，形成一个分布式、去中心化的浏览器到浏览器网络，以实现高效的文件传输。

🌐 Using open web standards, WebTorrent connects website users together to form a distributed, decentralized browser-to-browser network for efficient file transfer.

你可以在这里看到 WebTorrent 的演示：webtorrent.io。

🌐 You can see a demo of WebTorrent in action here: webtorrent.io.

为什么这很酷？​

🌐 Why is this cool?

想象一个类似 YouTube 的视频网站，但访客会帮助托管网站的内容。使用 WebTorrent 技术的网站用户越多，它就越快，也越可靠。

🌐 Imagine a video site like YouTube, but where visitors help to host the site's content. The more people that use a WebTorrent-powered website, the faster and more resilient it becomes.

浏览器之间的通信省去了中间环节，让人们可以按照自己的方式进行交流。不再需要客户端/服务器——只是一个平等的点对点网络。WebTorrent 是重新去中心化网络旅程的第一步。

🌐 Browser-to-browser communication cuts out the middle-man and lets people communicate on their own terms. No more client/server – just a network of peers, all equal. WebTorrent is the first step in the journey to re-decentralize the Web.

Electron 在其中扮演什么角色？​

🌐 Where does Electron come into the picture?

大约一年前，我们决定开发 WebTorrent Desktop，这是一个作为桌面应用运行的 WebTorrent 版本。

🌐 About one year ago, we decided to build WebTorrent Desktop, a version of WebTorrent that runs as a desktop app.

我们创建 WebTorrent Desktop 有三个原因：

🌐 We created WebTorrent Desktop for three reasons:

1. 我们想要一款简洁、轻量、无广告的开源种子应用。
2. 我们想要一个能够良好支持流媒体的种子应用。
3. 我们需要一个可以连接 BitTorrent 和 WebTorrent 网络的“混合客户端”

如果我们已经可以在 Web 浏览器中下载种子，为什么还要开发桌面应用？​

🌐 If we can already download torrents in my web browser, why a desktop app?

首先，简单介绍一下 WebTorrent 的设计背景。

🌐 First, a bit of background on the design of WebTorrent.

在早期，BitTorrent 使用 TCP 作为其传输协议。后来，uTP 出现了，承诺比 TCP 提供更好的性能和额外优势。每个主流的种子客户端最终都采用了 uTP，而如今你可以通过任一协议使用 BitTorrent。WebRTC 协议是下一个合乎逻辑的步骤。它带来了与网页浏览器互操作的可能性——一个由所有桌面 BitTorrent 客户端和数百万网页浏览器组成的庞大 P2P 网络。

🌐 In the early days, BitTorrent used TCP as its transport protocol. Later, uTP came along promising better performance and additional advantages over TCP. Every mainstream torrent client eventually adopted uTP, and today you can use BitTorrent over either protocol. The WebRTC protocol is the next logical step. It brings the promise of interoperability with web browsers – one giant P2P network made up of all desktop BitTorrent clients and millions of web browsers.

“网页节点”（在网页浏览器中运行的种子节点）通过增加数百万新的节点并将 BitTorrent 扩展到数十种新的使用场景，从而使 BitTorrent 网络更加强大。WebTorrent 尽可能严格地遵循 BitTorrent 规范，以便现有的 BitTorrent 客户端可以轻松添加对 WebTorrent 的支持。

一些像 Vuze 这样的种子应用已经支持网页端节点，但我们不想等其他应用去添加支持。所以基本上，WebTorrent Desktop 是我们加速 WebTorrent 协议普及的一种方式。 通过制作一个人们真正想使用的超棒种子应用，我们增加了网络中可以与网页端节点共享种子的节点数量（即网站上的用户）。

🌐 Some torrent apps like Vuze already support web peers, but we didn't want to wait around for the rest to add support. So basically, WebTorrent Desktop was our way to speed up the adoption of the WebTorrent protocol. By making an awesome torrent app that people really want to use, we increase the number of peers in the network that can share torrents with web peers (i.e. users on websites).

除了人们已知的功能之外，torrent 还有哪些有趣的用例？​

🌐 What are some interesting use cases for torrents beyond what people already know they can do?

WebTorrent 最令人兴奋的用途之一是对等辅助传输。像 维基百科 和 互联网档案馆 这样的非营利项目可以通过让访问者参与来减少带宽和托管成本。热门内容可以通过浏览器间直接传输，快速且廉价。很少访问的内容则可以通过 HTTP 从源服务器可靠地提供。

🌐 One of the most exciting uses for WebTorrent is peer-assisted delivery. Non-profit projects like Wikipedia and the Internet Archive could reduce bandwidth and hosting costs by letting visitors chip in. Popular content can be served browser-to-browser, quickly and cheaply. Rarely-accessed content can be served reliably over HTTP from the origin server.

互联网档案馆实际上已经更新了他们的种子文件，使其可以很好地与 WebTorrent 配合使用。因此，如果你想在你的网站上嵌入互联网档案馆的内容，你可以以一种减少档案馆托管成本的方式来做，从而让他们能够将更多资金用于真正的网络档案保存！

🌐 The Internet Archive actually already updated their torrent files so they work great with WebTorrent. So if you want to embed Internet Archive content on your site, you can do it in a way that reduces hosting costs for the Archive, allowing them to devote more money to actually archiving the web!

还有一些令人兴奋的商业用例，从 CDN 到通过 P2P 交付应用。

🌐 There are also exciting business use cases, from CDNs to app delivery over P2P.

你最喜欢的使用 WebTorrent 的项目有哪些？​

🌐 What are some of your favorite projects that use WebTorrent?

用 WebTorrent 构建的最酷的东西，毫无疑问，可能是 Gaia 3D 星图。它是一个流畅的 3D 交互式银河系模拟。数据通过 torrent 在你的浏览器中加载。飞越我们的恒星系统时，你会被震撼，同时意识到与宇宙的浩瀚相比，我们人类是多么渺小。

🌐 The coolest thing built with WebTorrent, hands down, is probably Gaia 3D Star Map. It's a slick 3D interactive simulation of the Milky Way. The data loads from a torrent, right in your browser. It's awe-inspiring to fly through our star system and realize just how little we humans are compared to the vastness of our universe.

你可以在《Torrenting The Galaxy》(https://medium.com/@flimshaw/torrenting-the-galaxy-extracting-2-million-3d-stars-from-180gb-of-csvs-457ff70c0f93) 中阅读这篇作品的制作进程，这是一篇博客文章，作者 Charlie Hoey 讲解了他是如何用 WebGL 和 WebTorrent 构建这张星图的。

🌐 You can read about how this was made in Torrenting The Galaxy, a blog post where the author, Charlie Hoey, explains how he built the star map with WebGL and WebTorrent.

我们也是 Brave 的超级粉丝。Brave 是一款可以自动阻止广告和追踪器的浏览器，从而让网页加载更快、更安全。Brave 最近增加了对种子文件的支持，因此你可以 在不使用单独应用的情况下查看传统种子。该功能由 WebTorrent 提供支持。

🌐 We're also huge fans of Brave. Brave is a browser that automatically blocks ads and trackers to make the web faster and safer. Brave recently added torrent support, so you can view traditional torrents without using a separate app. That feature is powered by WebTorrent.

所以，就像大多数浏览器可以渲染 PDF 文件一样，Brave 也可以渲染磁力链接和种子文件。它们只是浏览器本地支持的另一种内容类型。

🌐 So, just like how most browsers can render PDF files, Brave can render magnet links and torrent files. They're just another type of content that the browser natively supports.

Brave 的联合创始人之一实际上是 Brendan Eich，他是 JavaScript 的创造者，而 JavaScript 正是我们编写 WebTorrent 所用的语言，因此我们认为 Brave 选择集成 WebTorrent 非常酷。

🌐 One of the co-founders of Brave is actually Brendan Eich, the creator of JavaScript, the language we wrote WebTorrent in, so we think it's pretty cool that Brave chose to integrate WebTorrent.

为什么选择在 Electron 上构建 WebTorrent 桌面？​

🌐 Why did you choose to build WebTorrent Desktop on Electron?

有一种说法认为 Electron 应用很“臃肿”，因为它们在每个应用中都包含了完整的 Chrome 内容模块。在某些情况下，这在一定程度上是正确的（Electron 应用的安装包通常约为 40MB，而特定操作系统的应用安装包通常约为 20MB）。

🌐 There is a meme that Electron apps are "bloated" because they include the entire Chrome content module in every app. In some cases, this is partially true (an Electron app installer is usually ~40MB, where an OS-specific app installer is usually ~20MB).

然而，在 WebTorrent Desktop 的情况下，我们几乎使用了每一个 Electron 功能，并且在正常操作进程中使用了许多 Chrome 功能。如果我们想为每个平台从零实现这些功能，开发我们的应用将需要多几个月甚至数年的时间，或者我们只能发布单个平台版本。

🌐 However, in the case of WebTorrent Desktop, we use nearly every Electron feature, and many dozens of Chrome features in the course of normal operation. If we wanted to implement these features from scratch for each platform, it would have taken months or years longer to build our app, or we would have only been able to release for a single platform.

只是为了让大家了解，我们使用了 Electron 的 dock 集成（显示下载进度）、菜单栏集成（在后台运行）、协议处理器注册（打开磁力链接）、防止休眠（在视频播放时防止休眠）以及 自动更新。至于 Chrome 的功能，我们也用了很多：<video> 标签（播放多种视频格式）、<track> 标签（支持字幕）、拖放支持，以及 WebRTC（在原生应用中使用起来并不简单）。

🌐 Just to get an idea, we use Electron's dock integration (to show download progress), menu bar integration (to run in the background), protocol handler registration (to open magnet links), power save blocker (to prevent sleep during video playback), and automatic updater. As for Chrome features, we use plenty: the <video> tag (to play many different video formats), the <track> tag (for closed captions support), drag-and-drop support, and WebRTC (which is non-trivial to use in a native app).

更不用说：我们的种子引擎是用 JavaScript 编写的，并假设存在大量 Node API，尤其是用于 TCP 和 UDP 套接字支持的 require('net') 和 require('dgram')。

🌐 Not to mention: our torrent engine is written in JavaScript and assumes the existence of lots of Node APIs, but especially require('net') and require('dgram') for TCP and UDP socket support.

基本上，Electron 正是我们所需要的，它拥有我们在创纪录的时间内交付一个稳定、精致的应用所需的全部功能。

🌐 Basically, Electron is just what we needed and had the exact set of features we needed to ship a solid, polished app in record time.

你最喜欢 Electron 的哪些方面？​

🌐 What are your favorite things about Electron?

WebTorrent 库作为一个开源副项目已经开发了两年。我们在四周内完成了 WebTorrent Desktop。 Electron 是我们能够如此快速构建和发布应用的主要原因。

🌐 The WebTorrent library has been in development as an open source side project for two years. We made WebTorrent Desktop in four weeks. Electron is the primary reason that we were able to build and ship our app so quickly.

正如 Node.js 让使用 jQuery 的前端程序员能够轻松进行服务器编程一样，Electron 让熟悉 Web 或 Node.js 开发的任何人都可以进行原生应用开发。Electron 极具赋能性。

🌐 Just as Node.js made server programming accessible to a generation of jQuery-using front-end programmers, Electron makes native app development accessible to anyone familiar with Web or Node.js development. Electron is extremely empowering.

网站和桌面客户端共享代码吗？​

🌐 Do the website and the Desktop client share code?

是的，webtorrent npm 包 可以在 Node.js、浏览器和 Electron 中运行。完全相同的代码可以在所有环境中执行——这就是 JavaScript 的魅力所在。它是当今的通用运行时。Java 小程序曾承诺“编写一次，处处运行”，但由于各种原因，这一愿景从未真正实现。相比其他平台，Electron 实际上最接近这一理想。

🌐 Yes, the webtorrent npm package works in Node.js, in the browser, and in Electron. The exact same code can run in all environments – this is the beauty of JavaScript. It's today's universal runtime. Java Applets promised "Write Once, Run Anywhere" apps, but that vision never really materialized for a number of reasons. Electron, more than any other platform, actually gets pretty darn close to that ideal.

在构建 WebTorrent 时，你遇到了哪些挑战？​

🌐 What are some challenges you've faced while building WebTorrent?

在应用的早期版本中，我们在提升用户界面性能方面遇到了困难。我们将种子引擎放在与主应用窗口绘制相同的渲染进程中，结果不出意外，每当种子引擎进行大量 CPU 活动（例如验证从节点接收到的种子块）时，应用就会变得很慢。

🌐 In early versions of the app, we struggled to make the UI performant. We put the torrent engine in the same renderer process that draws the main app window which, predictably, led to slowness anytime there was intense CPU activity from the torrent engine (like verifying the torrent pieces received from peers).

我们通过将种子引擎移到第二个不可见的渲染进程来解决这个问题，我们通过IPC与该进程进行通信。这样，如果该进程短时间内使用大量 CPU，UI 线程也不会受到影响。流畅的滚动和动画非常令人满意。

🌐 We fixed this by moving the torrent engine to a second, invisible renderer process that we communicate with over IPC. This way, if that process briefly uses a lot of CPU, the UI thread will be unaffected. Buttery-smooth scrolling and animations are so satisfying.

注意：我们不得不将种子引擎放在渲染进程中，而不是“主”进程中，因为我们需要访问 WebRTC（它只在渲染进程中可用）。

🌐 Note: we had to put the torrent engine in a renderer process, instead of a "main" process, because we need access to WebRTC (which is only available in the renderer.)

Electron 应该在哪些方面改进？​

🌐 In what areas should Electron be improved?

我们非常希望看到更好的关于如何构建和发布生产就绪应用的文档，尤其是像代码签名和自动更新这样棘手的话题。我们不得不通过研究源代码和在推特上询问来了解最佳实践！

🌐 One thing we'd love to see is better documentation about how to build and ship production-ready apps, especially around tricky subjects like code signing and auto-updating. We had to learn about best practices by digging into source code and asking around on Twitter!

WebTorrent 桌面版完成了吗？如果还没完成，接下来会有什么更新？​

🌐 Is WebTorrent Desktop done? If not, what's coming next?

我们认为当前版本的 WebTorrent Desktop 非常出色，但总有改进的空间。我们目前正在努力改进界面细节、性能、字幕支持以及视频编码支持。

🌐 We think the current version of WebTorrent Desktop is excellent, but there's always room for improvement. We're currently working on improving polish, performance, subtitle support, and video codec support.

如果你有兴趣参与这个项目，可以查看我们的 GitHub 页面！

🌐 If you're interested in getting involved in the project, check out our GitHub page!

有哪些 Electron 开发技巧可能对其他开发者有用？​

🌐 Any Electron development tips that might be useful to other developers?

Feross，WebTorrent Desktop的贡献者之一，最近在NodeConf阿根廷大会上做了题为《现实世界的Electron：使用JavaScript构建跨平台桌面应用》的演讲，其中包含发布高质量Electron应用的实用技巧。如果你正处在已经有了一个基本可运行应用，并且希望将其提升到更高的精致度和专业水平的阶段，这次演讲特别有用。

在这里观看:

幻灯片在这里：

DC，另一位 WebTorrent 贡献者，写了一份可以让你的应用看起来更专业、更原生的清单。它包含代码示例，并涵盖了 macOS 停靠栏整合、拖放、桌面通知，以及确保应用快速加载等内容。

Electron 1.6.3 测试版包含对 macOS [触控栏] 的初步支持。

🌐 The Electron 1.6.3 beta release contains initial support for the macOS Touch Bar.

新的 Touch Bar API 允许你添加按钮、标签、弹出窗口、颜色选择器、滑块和间隔符。这些元素可以动态更新，并且在与之交互时也会触发事件。

🌐 The new Touch Bar API allows you to add buttons, labels, popovers, color pickers, sliders, and spacers. These elements can be dynamically updated and also emit events when they are interacted with.

这是该 API 的第一个版本，因此它将在接下来的几个 Electron 版本中不断发展。请查看发行说明以获取更多更新，并针对任何问题或缺失的功能提交问题。

🌐 This is the first release of this API so it will be evolving over the next few Electron releases. Please check out the release notes for further updates and open issues for any problems or missing functionality.

你可以通过 npm install electron@beta 安装此版本，并在 TouchBar 和 BrowserWindow Electron 文档中了解更多信息。

🌐 You can install this version via npm install electron@beta and learn more about it in the TouchBar and BrowserWindow Electron docs.

非常感谢 @MarshallOfSound 为 Electron 做出贡献。🎉

🌐 Big thanks to @MarshallOfSound for contributing this to Electron. 🎉

Touch Bar 示例​

🌐 Touch Bar Example

下面是一个在触控栏上创建简单老虎机游戏的示例。它演示了如何创建触控栏、设置项目样式、将其与窗口关联、处理按钮点击事件以及动态更新标签。

🌐 Below is an example of creating a simple slot machine game in the touch bar. It demonstrates how to create a touch bar, style the items, associate it with a window, handle button click events, and update the labels dynamically.

const { app, BrowserWindow, TouchBar } = require('electron');

const { TouchBarButton, TouchBarLabel, TouchBarSpacer } = TouchBar;

let spinning = false;

// Reel labels
const reel1 = new TouchBarLabel();
const reel2 = new TouchBarLabel();
const reel3 = new TouchBarLabel();

// Spin result label
const result = new TouchBarLabel();

// Spin button
const spin = new TouchBarButton({
  label: '🎰 Spin',
  backgroundColor: '#7851A9',
  click: () => {
    // Ignore clicks if already spinning
    if (spinning) {
      return;
    }

    spinning = true;
    result.label = '';

    let timeout = 10;
    const spinLength = 4 * 1000; // 4 seconds
    const startTime = Date.now();

    const spinReels = () => {
      updateReels();

      if (Date.now() - startTime >= spinLength) {
        finishSpin();
      } else {
        // Slow down a bit on each spin
        timeout *= 1.1;
        setTimeout(spinReels, timeout);
      }
    };

    spinReels();
  },
});

const getRandomValue = () => {
  const values = ['🍒', '💎', '7️⃣', '🍊', '🔔', '⭐', '🍇', '🍀'];
  return values[Math.floor(Math.random() * values.length)];
};

const updateReels = () => {
  reel1.label = getRandomValue();
  reel2.label = getRandomValue();
  reel3.label = getRandomValue();
};

const finishSpin = () => {
  const uniqueValues = new Set([reel1.label, reel2.label, reel3.label]).size;
  if (uniqueValues === 1) {
    // All 3 values are the same
    result.label = '💰 Jackpot!';
    result.textColor = '#FDFF00';
  } else if (uniqueValues === 2) {
    // 2 values are the same
    result.label = '😍 Winner!';
    result.textColor = '#FDFF00';
  } else {
    // No values are the same
    result.label = '🙁 Spin Again';
    result.textColor = null;
  }
  spinning = false;
};

const touchBar = new TouchBar([
  spin,
  new TouchBarSpacer({ size: 'large' }),
  reel1,
  new TouchBarSpacer({ size: 'small' }),
  reel2,
  new TouchBarSpacer({ size: 'small' }),
  reel3,
  new TouchBarSpacer({ size: 'large' }),
  result,
]);

let window;

app.once('ready', () => {
  window = new BrowserWindow({
    frame: false,
    titleBarStyle: 'hidden-inset',
    width: 200,
    height: 200,
    backgroundColor: '#000',
  });
  window.loadURL('about:blank');
  window.setTouchBar(touchBar);
});