NaN in tile parameters

[lavahot]

When using browserify to create a bundle suitable for browsers, at some point along the line the z, x, and y parameters are passed NaN. This, of course, fails.

[anandthakker]

Hmm, could you provide some more context? I've definitely used vt-geojson with browserify without problems, so maybe there's something more specific causing the problem...

[lavahot]

Thanks for responding so quickly. The exact URI I pass to vtgeojson is: "tilejson+https://api.mapbox.com/v4/" + {map_name} + ".json?access_token=" + {access_key}.
My options are set as: { bounds: {A turf.js generated feature collection}, strict: true }

[lavahot]

More specifically, the tilejson resolves to this source: https://a.tiles.mapbox.com:80/v4/MAP_NAME/NaN/NaN/NaN.vector.pbf?access_token=ACCESS_TOKEN, which results in a protocol error (which I also raised an issue for), but when the port specifier is removed, results in a 404.

[lavahot]

So I narrowed it down to something in tile-cover that is generating the tile indexes. The cover.tiles() calls are apparently not working correctly, even when valid GeoJSON are being passed to them. I'm not sure if it will help, but it looks like the dependency is out of date at 2.4.1, whereas the latest is 3.0.1. I tried to fix this in #11, but it looks like updating the outdated packages breaks a bunch of things. I have to put this on the back burner for now, but I know I'll need this functionality eventually so I might come back and debug those breaks.