Reaction: Node Module install not working on Dev branch host key verification failed

[hrath2015]

Expected behavior

reaction init should complete successfully.

Actual Behavior

meteor npm install is failing on Development branch. windows 10

Steps to Reproduce the Behavior

reaction init -b development

Versions

(run reaction -v from your reaction directory)

For enhancements or other issues, please describe in as much detail as
possible how the app should be changed and how this would benefit
users/developers

[hrath2015]

master branch is fine.

[hrath2015]

"braintree": "^2.0.2" is causing this. Not sure why.

[hrath2015]

It is similar to issue we had with authorize-net@github:ongoworks/node-authorize-net module. #1450

command npm install braintree works and meteor npm install braintree fails. In recent version 2.1.1 , of braintree a change is made where
let wrapPrototype = require('wrap-promise').wrapPrototype;
is changed to
let wrapPrototype = require('**@braintree/wrap-promise**').wrapPrototype;
when it connects to git as meteor npm results in error.

[awadesmoline]

I have tried reproducing this issue on mac, but I didn't get the error. Need a windows 10 OS to reproduce.

[hrath2015]

@awadesmoline May be you can co ordinate with Mike Murray, he knows how to reproduce windows issues by launching a windows VM.

[Tyler-Churchill]

I had this issue today

It happened when using the reaction-cli with "reaction init"
I also had the same "Host key verification failed" messaged when I cloned directly with git bash/cmd
On windows 10 Home 1607 14393.1480 64 bit

I reinstalled meteor/git and the problem has disappeared.

Edit:: NEVERMIND
still getting errors

I feel like I have tried everything in my power to get it to work

Second edit:: I ran reaction -v and I got all blank versions. Perhaps its my own error. I have done lots of meteor development on this machine before

[tdxiong]

I am also having this kind of error on Win 10 64bit, by following the requirements and installation instructions on the Reaction doc page. Anyone has a solution?

[zenweasel]

Verified this is fixed in latest master