Upgrade versions of JS libraries

[RickMohr]

As of today (9/21/2016), npm-check-updates reports:

 autotrack            ^0.6.5  →   ^1.0.3
 baconjs                ~0.6  →     ~0.7
 console-browserify   ~1.0.1  →   ~1.1.0
 dragula              ^2.0.2  →   ^3.7.2
 esri-leaflet         ~1.0.2  →   ~2.0.3
 leaflet-pip          ~0.1.1  →   ~1.0.0
 lodash                2.4.x  →   4.16.x
 moment               ~2.2.1  →  ~2.15.1
 mustache             ~0.7.2  →   ~2.2.1
 ramda                 0.5.x  →   0.22.x
 sanitize-filename    ~1.4.2  →   ~1.6.0
 chai                 ~1.8.1  →   ~3.5.0
 css-loader          ^0.23.1  →  ^0.25.0
 mocha               ~1.14.0  →   ~3.0.2
 testem               ^0.9.2  →  ^1.12.0

The following dependencies are satisfied by their declared version range, but the installed versions are behind. You can install the latest versions without modifying your package file by using npm update. If you want to update the dependencies in your package file anyway, use ncu -a/--upgradeAll.

 glob                 ^7.0.5  →   ^7.1.0
 jshint               ^2.9.2  →   ^2.9.3
 node-sass            ^3.5.3  →  ^3.10.0
 sass-loader          ^4.0.0  →   ^4.0.2
 webpack             ^1.13.1  →  ^1.13.2
 webpack-dev-server  ^1.14.1  →  ^1.16.1

[RickMohr]

Note that we're on version 0.6.22 of baconjs, which is 3 years old. There have been 88 releases since then.

The release notes list just one potentially backwards-incompatible change. I found and updated one place in the code in response to that. I did a moderate amount of testing (modeling, adding trees/resources, field configuration) and found no issues. There is certainly much JS code I did not test.

Probably we should upgrade everything right after a release so we have a while for extra-thorough testing.