Depending on cutting-room-floor module about mapbox-tile-copy

[mapsam]

While we're here, let's update dependencies to get rid of these warnings:

npm WARN deprecated [email protected]: Package abandoned, contact [email protected] for more info.
npm WARN deprecated [email protected]: This module is now under the @mapbox namespace: install @mapbox/tiletype instead
npm WARN deprecated [email protected]: This module has moved: please install @mapbox/vector-tile instead
npm WARN engine [email protected]: wanted: {"node":"0.8.x || 0.10.x"} (current: {"node":"4.8.4","npm":"2.15.11"})
npm WARN deprecated [email protected]: renamed to d3-queue
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated [email protected]: This module has moved: please install @mapbox/point-geometry instead
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: protozero should no longer be used via npm, install instead via https://github.com/mapbox/mason

[springmeyer]

@mapsam 🍎

[rclark]

https://github.com/mapbox/mapbox-geostats was the intended replacement for tile-stat-stream. But my memory is hazy -- not sure if its an easy fit or not.

I was pretty sure we'd worked mapbox-geostats into our downstream tile-generation service, which makes me wonder if any tile statistics that are being generated by this repository are just being ignored?

[mapsam]

Correct, we're using mapbox-geostats now and are not using the stats or --stats option from mapbox-tile-copy. As far as next steps, I suggest:

🍎 a new major release completely removing stats generation
🍌 updating stats generation to only happen if stats are passed as an option. Right now it seems that we generate stats every run, and only write them out if the user requests it. Let's not even compute them unless a user requests it.

[springmeyer]

Great, thank you @rclark and @mapsam - that plan sounds great.

[mapsam]

@springmeyer just to confirm - are you in favor of 🍎 or 🍌 ?

[mapsam]

Working over in #107

Some upstream updates will be necessary to get rid of all these module warnings 😞 (including mapnik). Here are the culprits

queue-async - I've updated this immediate module to use d3-queue, but this will persist until tilelive and tilelive-omnivore are updated.

$ npm ls queue-async
@mapbox/[email protected] /Users/mapsam/mapbox/mapbox-tile-copy
├─┬ @mapbox/[email protected]
│ └── [email protected] 
└─┬ @mapbox/[email protected]
  └── [email protected] 

tough-cookie - these are largely in some big upstream modules that will largely be fixed by updating request in all of them (no small feat) and updating node-sqlite3

$ npm ls tough-cookie
@mapbox/[email protected] /Users/mapsam/mapbox/mapbox-tile-copy
├─┬ @mapbox/[email protected]
│ └─┬ [email protected]
│   └── [email protected] 
├─┬ @mapbox/[email protected]
│ └─┬ @mapbox/[email protected]
│   └─┬ [email protected]
│     └── [email protected] 
├─┬ @mapbox/[email protected]
│ └─┬ [email protected]
│   └── [email protected] 
├─┬ [email protected]
│ └─┬ [email protected]
│   └─┬ [email protected]
│     └── [email protected] 
└─┬ [email protected]
  └── [email protected] 

node-uuid - will be fixed by updating request.js in tilelive-vector

$ npm ls node-uuid
@mapbox/[email protected] /Users/mapsam/mapbox/mapbox-tile-copy
└─┬ @mapbox/[email protected]
  └─┬ [email protected]
    └── [email protected] 

minimatch ✅ fixed by updating tape

protozero - requires update to mapnik/mapnik-vector-tile to install via mason instead of NPM

$ npm ls protozero
@mapbox/[email protected] /Users/mapsam/mapbox/mapbox-tile-copy
└─┬ [email protected]
  └── [email protected] 

[springmeyer]

protozero - requires update to mapnik/mapnik-vector-tile to install via mason instead of NPM

This will depend on mapbox/mason#396, unless we shortcut by using a git submodule (currently done as a hack in node-mapnik for geometry.hpp)