Zeke Sikelianos

Opened https://github.com/electron/electron/pull/12783. Had I known this was the default behavior, I probably would not have implemented the dialog in this module! cc @leo

Oooh good catch. That's not good. I've made you a proofreader, per your request, so you should be able to fix this one-off. But yeah we should probably add something...

Thanks for creating this issue. I didn't know that the README was making it through to the website. Does anything link to this? My hope is that this file (`/docs/README/md`...

While it won't solve the fundamental problem here, folks might be able to improve uptime by using wzrd.in as a build service rather than a runtime service. See these projects...

Wow I hadn't noticed that this module got a recent refresh. Thanks @wooorm 🙌

The nodejs/i18n Working Group has converged on a pattern for managing multiple versions of Node.js: https://github.com/nodejs/i18n/pull/83 It looks like this: ```sh $ tree content -d -L 2 ├── v10.x │  ...

For all the folks looking for S3 support, this may be helpful: https://github.com/jbuck/npm-readonly-mirror

Great feedback, @AoDev. Thanks for posting. There is definitely room for improvement here. > Your builds are code-signed Here's a PR that kicks off a code-signing tutorial: https://github.com/electron/electron/pull/12767 -- once...

> can't people just create a "release repo", where they add the binaries to the releases I hadn't considered that, but it's a great idea! > open source pet project...

@Tapestes if you're using the [update-electron-app](https://github.com/electron/update-electron-app) module, then yes the repo is read from your package.json file. It can also be in this form: ``` "repository": "https://github.com/Cogulator/Cogulator" ``` ... both...