You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
danielcobo
It seems the dependency used for following changes in CouchDB could be outdated.
Running npm install nano on a current version of Node will log npm WARN engine follow@0.12.1: wanted: {"node":"0.12.x || 0.10.x || 0.8.x"} (current: {"node":"4.2.2","npm":"2.14.7"})
The issue has been already raised at the repository of the dependency, however it looks like it has not yet been resolved - iriscouch/follow#73
Original issue
danielcobo
It seems the dependency used for following changes in CouchDB could be outdated.
Running npm install nano on a current version of Node will log npm WARN engine follow@0.12.1: wanted: {"node":"0.12.x || 0.10.x || 0.8.x"} (current: {"node":"4.2.2","npm":"2.14.7"})
The issue has been already raised at the repository of the dependency, however it looks like it has not yet been resolved - iriscouch/follow#73
satazor
Getting the same issue. The README points to https://github.com/jhs/follow/blob/master/package.json#L11 which has the issue resolved, but irishcoush's follow is being used instead of jh's fork. I'm confused.
collinsrj
nsp flags this as a security issue:
nano@6.2.0 > follow@0.12.1 > request@2.55.0 > hawk@2.3.1
There is a CVE open against hawk. See here https://nodesecurity.io/advisories/77
The text was updated successfully, but these errors were encountered: