ide / dash-button Goto Github PK

The devDependency @types/node was updated from 12.7.5 to 12.7.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency eslint-config-universe was updated from 2.0.0 to 2.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-universe is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I have no clue how this works, but i just found this:

https://github.com/badbeef/Amazon-Dash-Server
http://blog.nemik.net/2015/08/dash-button-corral/

If your scripts return a 200 OK HTTP response, the Buttons will even light up green to say that all is cool.

Maybe this helps

The devDependency rimraf was updated from 2.6.2 to 2.6.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rimraf is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

When I try to do 'sudo npm run scan' I get this error. If I just try to remove 'use strict' from that file, it breaks it in another way. How can I make this work? I'm on OS X. I tried updating node. Here's the error:

/Users/kevinthr/Dropbox/Work/n04 dash/node_modules/dash-button/build/cli.js:29
let parser = _yargs2.default.usage('Usage: $0 <command> [options]').command(
^^^
SyntaxError: Unexpected strict mode reserved word
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:906:3

The devDependency @typescript-eslint/eslint-plugin was updated from 2.3.0 to 2.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @typescript-eslint/parser was updated from 2.3.0 to 2.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/parser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Installed packages:

• npm v3.5.2
• node v4.2.6
• libpcap-dev

The devDependency eslint was updated from 6.4.0 to 6.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I'm seeing errors on install and scan that look like node version issues but I've tried this with Node 6, Node 8, and Node 10, all with no success.

I installed Node via nvm which actually doesn't allow you to run sudo npm run scan. It initially gives an error saying sudo: npm: command not found and then I have to create a symlink for it to work.

This can't be caused by nvm can it? I'd prefer not to blow away nvm and install via apt-get.

Version details

Node version: v8.15.0
npm version: 6.4.1
nvm version: 0.34.0
OS: Linux raspberrypi 4.9.80+ #1098 Fri Mar 9 18:51:28 GMT 2018 armv6l GNU/Linux

Error messages

$ npm install --save dash-button

> [email protected] install /home/pi/dash-listener/node_modules/socketwatcher
> node-gyp rebuild

make: Entering directory '/home/pi/dash-listener/node_modules/socketwatcher/build'
  CXX(target) Release/obj.target/socketwatcher/socket_watcher.o
../socket_watcher.cpp: In static member function ‘static void SocketWatcher::Callback(uv_poll_t*, int, int)’:
../socket_watcher.cpp:77:60: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
   Nan::MakeCallback(watcher->handle(), callback, argc, argv);
                                                            ^
In file included from ../socket_watcher.hpp:8:0,
                 from ../socket_watcher.cpp:5:
../../nan/nan.h:959:46: note: declared here
   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                              ^~~~~~~~~~~~
../socket_watcher.cpp: In static member function ‘static void SocketWatcher::New(const Nan::FunctionCallbackInfo<v8::Value>&)’:
../socket_watcher.cpp:104:49: warning: ‘v8::Local<v8::Object> v8::Function::NewInstance() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
     info.GetReturnValue().Set(cons->NewInstance());
                                                 ^
In file included from /home/pi/.node-gyp/8.15.0/include/node/v8.h:26:0,
                 from /home/pi/.node-gyp/8.15.0/include/node/node.h:63,
                 from ../../nan/nan.h:53,
                 from ../socket_watcher.hpp:8,
                 from ../socket_watcher.cpp:5:
/home/pi/.node-gyp/8.15.0/include/node/v8.h:3901:52: note: declared here
   V8_DEPRECATED("Use maybe version", Local<Object> NewInstance() const);
                                                    ^
/home/pi/.node-gyp/8.15.0/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
  SOLINK_MODULE(target) Release/obj.target/socketwatcher.node
  COPY Release/socketwatcher.node
make: Leaving directory '/home/pi/dash-listener/node_modules/socketwatcher/build'

> pcap@git+https://github.com/mranney/node_pcap.git#b4eb828fbfb3ad9a253351aa38cb41c203589712 install /home/pi/dash-listener/node_modules/pcap
> node-gyp rebuild

make: Entering directory '/home/pi/dash-listener/node_modules/pcap/build'
  CXX(target) Release/obj.target/pcap_binding/pcap_binding.o
  CXX(target) Release/obj.target/pcap_binding/pcap_session.o
../pcap_session.cc: In static member function ‘static void PcapSession::New(const Nan::FunctionCallbackInfo<v8::Value>&)’:
../pcap_session.cc:46:49: warning: ‘v8::Local<v8::Object> v8::Function::NewInstance() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
     info.GetReturnValue().Set(cons->NewInstance());
                                                 ^
In file included from /home/pi/.node-gyp/8.15.0/include/node/v8.h:26:0,
                 from /home/pi/.node-gyp/8.15.0/include/node/node.h:63,
                 from ../../nan/nan.h:53,
                 from ../pcap_session.h:4,
                 from ../pcap_session.cc:7:
/home/pi/.node-gyp/8.15.0/include/node/v8.h:3901:52: note: declared here
   V8_DEPRECATED("Use maybe version", Local<Object> NewInstance() const);
                                                    ^
/home/pi/.node-gyp/8.15.0/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../pcap_session.cc: In static member function ‘static void PcapSession::PacketReady(u_char*, const pcap_pkthdr*, const u_char*)’:
../pcap_session.cc:85:102: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
 Nan::GetCurrentContext()->Global(), Nan::New(session->packet_ready_cb), 0, NULL);
                                                                                ^
In file included from ../pcap_session.h:4:0,
                 from ../pcap_session.cc:7:
../../nan/nan.h:959:46: note: declared here
   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                              ^~~~~~~~~~~~
  SOLINK_MODULE(target) Release/obj.target/pcap_binding.node
  COPY Release/pcap_binding.node
make: Leaving directory '/home/pi/dash-listener/node_modules/pcap/build'
npm WARN [email protected] No description
npm WARN [email protected] No repository field.

+ [email protected]
added 57 packages from 24 contributors and audited 66 packages in 147.145s
found 0 vulnerabilities

Running scan seems to give similar node version type of errors.

$ sudo npm run scan
/home/pi/.nvm/versions/node/v8.15.0/lib/node_modules/npm/bin/npm-cli.js:85
      let notifier = require('update-notifier')({pkg})
      ^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Function.Module.runMain (module.js:441:10)
    at startup (node.js:140:18)
    at node.js:1043:3

The devDependency @types/jest was updated from 24.0.18 to 24.0.19.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/jest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/yargs was updated from 13.0.2 to 13.0.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/yargs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency yargs was updated from 14.1.0 to 14.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

yargs is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.6.0 to 7.6.2.

• The devDependency @babel/preset-env was updated from 7.6.0 to 7.6.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 1.1.0 of nullthrows was just published.

This version is covered by your current version range and after updating it in your project the build failed.

nullthrows is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency prettier was updated from 1.14.2 to 1.14.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency prettier was updated from 1.18.2 to 1.19.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

It appears that "new" model Dash buttons (they have finally been released in the UK, and I'm playing with one on the day of release) behave differently when connecting to the network than the previous models.

Rather than broadcasting an ARP request from 0.0.0.0, they instead broadcast a DHCP request from 0.0.0.0. They do then send out ARP requests for other network devices (e.g. the gateway), but these have the source IP set to the address allocated to the device.

The following patch to build/ArpProbes.js fixes this, and should properly handle both the new and old button varieties. Change:

const ARP_PROBE_FILTER = 'arp src host 0.0.0.0';

to

const ARP_PROBE_FILTER = '(arp or (udp and src port 68 and dst port 67)) and src host 0.0.0.0';

(I believe udp and src port 68 and dst port 67 is the most succinct way to filter DHCP request packets.)