The latest version of electron-builder lets us use file macros in the file
patterns such as `$platform`, which is useful for us to be able to
include platform specific files in the build as DRY as possible.
Only one of these files was being used, and they were going out of step
relative to one another.
Put rpc.proto in the resources directory for consistency with other
vendored resources, i.e. the lnd binary
Updated the def from:
https://github.com/lightningnetwork/lnd/blob/master/lnrpc/rpc.proto
From stylefmt's readme:
Consider other tools before adopting stylefmt
If you are using stylefmt with stylelint configuration to format according
to its rules, you can now use stylelint's --fix option (from v7.11.0) to autofix.
And declare minimum versions in package.json.
Node 7 was a dev release and is defunct now that 8 is LTS and 9 is the
current dev release. If we wanted to support earlier versions, we should
go all the way back to the prior LTS release series, 6, but I don't see
a reason to do that for new software.
Bump to npm 5 because that is the version that was released with node 8:
https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V8.md#8.0.0
This was prompted by the fact that current versions of yarn have dropped node 7
support.
https://yarnpkg.com/en/
It's used by flow:
Launching Flow server for /.../zap-desktop
Spawned flow server (pid=46193)
Logs will go to /private/tmp/flow/zSUserszSbenzSDevelopmentzSBitcoinzSzZap-desktop.log
app/main.dev.js:18
18: import { lookup } from 'ps-node'
^^^^^^^^^ ps-node. Required module not found
Found 1 error
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! zap-desktop@0.0.1 flow: `flow`
npm ERR! Exit status 2
Tom Kirkpatrick
Ben Woosley
Jack Mallers
João Almeida
Jim Posen