johnny-five no longer builds

[pohly]

Seen in refkit (https://bugzilla.yoctoproject.org/show_bug.cgi?id=11425), but probably also happens elsewhere:

ERROR: johnny-five-0.9.59-r0 do_install: Function failed: do_install (log file is located at /fast/build/refkit/intel-corei7-64/tmp-glibc/work/corei7-64-refkit-linux/johnny-five/0.9.59-r0/temp/log.do_install.8675)
ERROR: Logfile of failure stored in: /fast/build/refkit/intel-corei7-64/tmp-glibc/work/corei7-64-refkit-linux/johnny-five/0.9.59-r0/temp/log.do_install.8675
Log data follows:
...
| DEBUG: Executing shell function do_install
| npm ERR! Linux 4.9.0-0.bpo.2-amd64
| npm ERR! argv "/fast/build/refkit/intel-corei7-64/tmp-glibc/work/corei7-64-refkit-linux/johnny-five/0.9.59-r0/recipe-sysroot-native/usr/bin/node" "/fast/build/refkit/intel-corei7-64/tmp-glibc/work/corei7-64-refkit-linux/johnny-five/0.9.59-r0/recipe-sysroot-native/usr/bin/npm" "install" "--prefix" "/fast/build/refkit/intel-corei7-64/tmp-glibc/work/corei7-64-refkit-linux/johnny-five/0.9.59-r0/image/usr" "-g" "--arch=x64" "--target_arch=x64" "--production" "--no-registry"
| npm ERR! node v4.5.0
| npm ERR! npm v2.15.9
|
| npm ERR! registry URL is required
| npm ERR!
| npm ERR! If you need help, you may report this error at:
| npm ERR! https://github.com/npm/npm/issues
| npm ERR! Linux 4.9.0-0.bpo.2-amd64
| npm ERR! argv "/fast/build/refkit/intel-corei7-64/tmp-glibc/work/corei7-64-refkit-linux/johnny-five/0.9.59-r0/recipe-sysroot-native/usr/bin/node" "/fast/build/refkit/intel-corei7-64/tmp-glibc/work/corei7-64-refkit-linux/johnny-five/0.9.59-r0/recipe-sysroot-native/usr/bin/npm" "install" "--prefix" "/fast/build/refkit/intel-corei7-64/tmp-glibc/work/corei7-64-refkit-linux/johnny-five/0.9.59-r0/image/usr" "-g" "--arch=x64" "--target_arch=x64" "--production" "--no-registry"
...

According to Paul Eggleton, that's "basically because some dependency in the .json file isn't being correctly satisfied, so npm thinks it needs a registry, but we are telling it not to use one and so it blows up".

[bluelightning]

I am still working on this BTW - I think the cause is several dependencies that have version set to "latest" in the package.json, which means npm thinks it needs to check for a later version. My proposed fix (which I've already started) is going to be to add code to npm.bbclass hack package.json to fix the version to the one we've already fetched.