-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Conversation
7d9d586
to
ff02c08
Compare
Node 10.2 was released yesterday, it includes a fix for Experimental fs.promise Warnings when they're not actually used that resulted in js-ipfs cli errors. Once all dependency PRs are merged and released I will update the dependencies in this PR. We should be good for node 10 support. |
@jacobheun dignifiedquire/lock-me#3 seems to have been merged and released - can I review this and get this merged? |
src/core/boot.js
Outdated
@@ -3,6 +3,7 @@ | |||
const waterfall = require('async/waterfall') | |||
const series = require('async/series') | |||
const extend = require('deep-extend') | |||
const RepoErrors = require('ipfs-repo/src/errors') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an anti-pattern. Can we expose the repo errors through require('ipfs-repo').errors
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch, and yes ipfs/js-ipfs-repo#171
package.json
Outdated
@@ -110,10 +110,10 @@ | |||
"ipfs-block": "~0.7.1", | |||
"ipfs-block-service": "~0.14.0", | |||
"ipfs-multipart": "~0.1.0", | |||
"ipfs-repo": "~0.20.0", | |||
"ipfs-repo": "^0.22.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should keep the ~
for packages below 1.0.0
, as stated in the js-ipfs guidelines.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch! :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, my mistake, ran the wrong install command. New ci build on the way!
👀 ing now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM. npm install
works locally and all the tests pass. Just waiting on the result from CI.
@jacobheun could you setup commit signing for next time? https://help.github.com/articles/signing-commits-using-gpg/ |
Opening this early to provide more visibility.
Update:
The jenkins builds are now running and working for node 10.0. There is an issue in node 10.1 with fs.promises warnings, mentioned below, but there is a fix already merged that should go out with the next release so I am going to leave that for now.
I will be working on getting all the dependency change PRs merged so I can get this PR finalized.
Things to fix:
Dependencies
The following PRs need to be completed prior to this release.